fix(everything): clarify resource link ID mapping#4503
Open
Joosboy wants to merge 1 commit into
Open
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.
Summary
get-resource-linksresource ID mapping in the Everything server docs.isOddname.Why
Issue #475 notes that odd/even resource wording can be confusing. The current Everything server uses dynamic
text/{resourceId}andblob/{resourceId}templates; this keeps the existing behavior and documents the mapping used byget-resource-links.Validation
npm test --workspace @modelcontextprotocol/server-everything -- __tests__/tools.test.tsnpm run build --workspace @modelcontextprotocol/server-everythingnpx prettier --check src/everything/tools/get-resource-links.ts src/everything/docs/features.mdRelated issue
Refs #475