modelcontextprotocol / modelcontextprotocol/conformance
Add conformance scenario: logging/setLevel and log notifications
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 127
- Forks
- 101
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
The logging utility (logging/setLevel and log message notifications) has no conformance scenario. The spec defines:
- Server MUST accept logging/setLevel with a valid severity level
- Server SHOULD only emit log notifications at or above the configured level
- Valid levels: debug, info, notice, warning, error, critical, alert, emergency
Proposed checks:
- Setting level to "error" stops debug/info/warning notifications
- Setting level to "debug" allows all notifications through
- Invalid level values are rejected appropriately
I'll submit a PR for this.
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 with the logging/setLevel entry point and the logging conformance scenario requirements in this issue. Add checks for valid severity levels, filtering at the configured threshold, allowing all levels at debug, and rejecting invalid values; done means these checks pass against the server.
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
- 67/100