callToolStream
AI overview
Sign in and the AI will write an overview from our coverage.
Headlines · 2
- MCP background task progress stalls after the original request closes
A local test using Streamable HTTP and MCP SDK 1.30 found that notifications/progress reached the client for only one of five background task steps because the originating request connection had closed. The author showed that updating statusMessage and polling tasks/get retrieved all five steps, while callToolStream surfaced four of five updates. These results apply to the tested local configuration, and the author notes that behavior may differ under other transports and timing conditions.
掘金 · 人工智能 · 🔥 1 - MCP task primitives tested in a note service
A hands-on report tests the MCP task primitives introduced in protocol version 2025-11-25: tasks/get, tasks/result, tasks/cancel and tasks/list. In the author’s note-service implementation, task creation returned in about four milliseconds and status updates arrived roughly once per second. The test also identified several operational issues: a client that had not called listTools() could silently fall back to synchronous execution; instance-local stores made tasks unavailable in a stateless setup; InMemoryTaskStore lost task data after a restart; and tasks/cancel changed task status without signaling the running background code. The report concludes that task primitives standardize how long-running tasks are invoked, while applications remain responsible for shared and durable storage, background execution and cancellation handling.
掘金 · 人工智能 · 🔥 0
Experience and discussion from the community
Share my callToolStream experienceAsk about callToolStream
Nobody has shared their experience with callToolStream yet.