test(everything): cover tool annotations during registration#4529
Open
jw-ond wants to merge 1 commit into
Open
test(everything): cover tool annotations during registration#4529jw-ond wants to merge 1 commit into
jw-ond wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds regression coverage for tool annotations in the Everything reference server registration tests.
The Everything server already demonstrates
readOnlyHint,destructiveHint,idempotentHint, andopenWorldHintacross its tools. This change makes that contract explicit in tests so future tool additions or refactors do not accidentally drop those annotations from standard, conditional, or task-based tool registrations.Publishing Your Server
Not applicable. This modifies an existing reference server test.
Server Details
Motivation and Context
Tool annotations are an important part of how MCP clients can reason about tool behavior before invocation. The Everything server is a reference implementation, so keeping annotation coverage explicit helps it remain a reliable example for client and server implementers.
How Has This Been Tested?
npm test --workspace @modelcontextprotocol/server-everything -- __tests__/registrations.test.tsnpm test --workspace @modelcontextprotocol/server-everythingnpm run build --workspace @modelcontextprotocol/server-everythinggit diff --checkBreaking Changes
None.
Types of changes
Checklist
Additional context
No runtime behavior changes. This only adds regression assertions around existing registration metadata.