The New Stack: Why MCP servers should tell agents what to do next
AWS developer advocate James Ward argues that MCP servers should return guidance with data, telling the agent what it just did, what it might do next, and where to find more. He describes AWS adding a session ID parameter to tools so individual calls can be traced as one journey, with a second parameter carrying the user's goal for evaluation. Ward also said AWS ships a CLI and skills alongside MCP because MCP's OAuth model cannot switch between AWS profiles the way the CLI can.
What changes for platform teams
Platform teams exposing MCP servers can add session and goal parameters to tools and build evals that compare user intent with agent paths, then adjust tool descriptions or batch tools based on observed patterns. The article presents these as AWS practices rather than a released standard, so no protocol change is implied.
Read the original at The New Stack ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules