Skip to content

fix(schema): add missing property descriptions across official MCP servers#3732

Open
radeshgovind-2005 wants to merge 2 commits intomodelcontextprotocol:mainfrom
radeshgovind-2005:fix/schema-property-descriptions
Open

fix(schema): add missing property descriptions across official MCP servers#3732
radeshgovind-2005 wants to merge 2 commits intomodelcontextprotocol:mainfrom
radeshgovind-2005:fix/schema-property-descriptions

Conversation

@radeshgovind-2005
Copy link
Copy Markdown

Motivation and Context

Fixes #3669

The official MCP reference servers were missing description fields on tool
input schema properties, and several tools in server-everything were missing
required arrays. LLMs use these descriptions to understand how to call tools
correctly — without them, the model has to guess parameter semantics from names
alone, which degrades tool-use accuracy. As reference implementations, these
servers set the standard the whole ecosystem follows.

How Has This Been Tested?

  • Verified all three servers build cleanly with tsc --noEmit (no new errors)
  • Ran the MCP Inspector (npx @modelcontextprotocol/inspector) and visually
    confirmed descriptions appear correctly on all modified tools including
    read_file, move_file, search_files, and others
  • Confirmed the required array fix works correctly by removing .default()
    values from parameters that should be explicitly required

Breaking Changes

No. All changes are purely additive (descriptions) or make implicit requirements
explicit (required arrays). No existing functionality was changed or removed.
Users do not need to update their MCP client configurations.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Changes across 6 files:

  • src/filesystem/index.ts — 18 descriptions added across all 11 tools
  • src/memory/index.ts — 4 descriptions added to array parameters
  • src/everything/tools/get-resource-reference.ts — description + required fix
  • src/everything/tools/get-resource-links.ts — required fix
  • src/everything/tools/gzip-file-as-resource.ts — required fix + resource description
  • src/everything/tools/trigger-long-running-operation.ts — required fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Schema quality: missing property descriptions across official MCP servers

1 participant