modelcontextprotocol / modelcontextprotocol/conformance
Add conformance scenario: progress notification edge cases
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 127
- Forks
- 101
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
The existing tools-call-with-progress scenario in tools.ts validates basic progress notification delivery. However, several spec requirements lack dedicated validation:
- Progress values MUST be non-decreasing across notifications for the same token
- If
totalis provided, it SHOULD remain consistent or increase progressSHOULD NOT exceedtotal- Progress notifications MUST reference the correct progressToken
- No progress notifications should be sent when no progressToken was provided in the request
- Progress notifications MUST cease after the request completes
I'll submit a PR adding a standalone progress-notifications scenario covering these edge cases.
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 in tools.ts by reading the existing tools-call-with-progress scenario and its progress notification checks. Add a standalone scenario covering monotonic progress, total consistency and bounds, token matching, absent-token behavior, and cessation after completion. Done means each listed edge case has dedicated conformance validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100