Understand this story
On October 29, 2026, James Ward, Principal Developer Advocate at AWS, proposed that MCP servers should not merely be APIs that "fetch data," but should attach guidance when returning data, telling the agent what it has just done and what it can do next. He also noted that MCP has no trace ID by default; AWS's approach is to add a session ID parameter to tools, having the agent pass it in on every call, thereby stringing individual calls into a complete chain. The same report mentions that AWS opened MCP Server to everyone in May this year and added Lambda diagnostics in September. Currently, this view has been reported by The New Stack, with no cross-verification from other sources or subsequent developments yet.
AI-generated from public reports
Latest development · Report
AWS's James Ward: MCP servers should tell agents what to do nextDevelopments
1 confirmed developments
James Ward proposes that MCP servers should guide the Agent's next action
Source:The New Stack
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 29
The New Stack
AWS's James Ward: MCP servers should tell agents what to do next
James Ward, Principal Developer Advocate at AWS, believes that MCP servers should not just be "data-fetching" APIs, but should include guidance when returning data, telling the agent what it just did and what it can do next. He also pointed out that MCP has no trace ID by default; AWS's approach is to add a session ID parameter to tools, having the agent pass it in on every call, thereby linking individual calls into a complete chain. AWS opened MCP Server to everyone in May this year, and added Lambda diagnostics in September.