modelcontextprotocol / modelcontextprotocol/typescript-sdk
consider defaulting resetTimeoutOnProgress to True
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
The tool calls can take an arbitrary amount of time (e.g. calls to external agents) so the progress mechanism is the only sane way of supporting tool calls of unknown/long duration since clients will not know a priori how long a request can take to set an appropriate timeout.
Because of the extensible nature of MCP, client developers will also not know how long operations are expected to take, or might not be aware of the implications of ignoring this parameter (breaking tool calls over 60s default timeout).
Please consider defaulting resetTimeoutOnProgress to True for a much better out-of-the-box experience.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the TypeScript definition and default handling for resetTimeoutOnProgress, then trace how progress and request timeouts interact for tool calls. Review the surrounding timeout and progress behavior before deciding whether the default can change without breaking existing clients; done means the new default is implemented consistently and its behavior is covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100