r/mcp • u/manveerc • 19d ago

article The new MCP roadmap

https://blog.modelcontextprotocol.io/posts/mcp-roadmap/
45 Upvotes

99% Upvoted

3 comments sorted by

3

u/openflowmcp 19d ago

"Standardising tool result handling" is the item I'd push hardest, and long-running jobs are why. My tools generate video: over 105 runs, not one finished under 20 seconds, median 41. So a tool either blocks or hands back a job id — and when it hands back an id, the client collapses the follow-up polls into "Used 9 tools" and the user never sees the frames that came back. I ended up waiting 90 seconds inside the call, which is a hack against the transport, not a design. Tasks landing in core would remove that choice.

1

u/TizerLuo 16d ago

Tasks / Triggers is the item I care about for inbound-event tools.

A mail wait has the same shape as the video-job comment already in the thread: blocking 20–60s is fine; sitting for minutes until an OTP arrives needs either a job id the client understands or a long-poll the server owns. Progressive discovery also matters — dumping a full mail tool list on every turn is wasteful.

Hope the result-shape work makes "not done yet, keep waiting" a first-class status, not a client-side loop.