Add conformance scenario: progress notification edge cases
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- testing
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.
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.
- Dominant language
- TypeScript
- Stars
- 127
- Forks
- 101
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 6
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.
More from modelcontextprotocol/conformance
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/conformance#315 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/conformance#312 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
All issues in modelcontextprotocol/conformance
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100