Skip to content

Update Server Documentation - #172

Open
below wants to merge 1 commit into
modelcontextprotocol:mainfrom
below:patch-1
Open

below wants to merge 1 commit into
modelcontextprotocol:mainfrom
below:patch-1

Conversation

@below

@below below commented Nov 25, 2025 •

Copy link
Copy Markdown

This allows tools like mcpInspector to list the tools

Add type' properties to the inputSchemain the documentation sample, and adjust theproperties` as expected by the current specification

Motivation and Context

The MCP Inspector will not list or use the tools these changes are done (See also here

How Has This Been Tested?

With MCP Inspector v0.17.2 and my own test implementation

Breaking Changes

Only Documentation

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 Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Possibly, this should be done automatically.

specification
This allows tools like mcpInspector to list the tools
@below below changed the title Add "type: object" to InputSchema Update Server Documentation Nov 26, 2025
@toasterbook88

Copy link
Copy Markdown

Maintainer triage on February 24, 2026: recommended close for backlog hygiene. This stale docs PR currently conflicts with main; reopen with a fresh rebase if these updates are still desired.

@varun06

varun06 commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Hi @below, thank you for this contribution. We're consolidating overlapping PRs.

#294 fixes the same README tool input schemas and applies cleanly to current main. (This version also has a stray backtick in inputSchema`:, so the example wouldn't compile.)

We plan to close this PR once #294 is merged, so the fix isn't lost in between. If you think something here isn't covered by #294, please comment there or here and we'll make sure it's carried over.

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.

3 participants