Skip to content

verify(fastmcp): native versus protocol tool descriptors (§10) #653

Open

Description

@msaleme

Summary

Complete the FastMCP §10 descriptor-attribute slice of the offline MCP/descriptor verification handoff. Distinguish native FastMCP tool objects from the MCP protocol tool representation rather than assuming both expose .inputSchema.

Plan

  • Install and inspect the MCP SDK's FastMCP and standalone fastmcp distribution, recording exact versions and package ownership.
  • Define a trivial native tool, assert the real name/description/schema accessors, and compare the framework's already-computed schema with its protocol tool representation without opening any MCP session.
  • Commit a reproducible sibling probe and output, correct the ledger and any code that names the disproven attributes, preserve the descriptor implementation guard, and document version-specific mismatches.
  • Run framework-free and all-framework gates separately, required lint/type/import checks, and synchronize the consumer boundary docs.

I am taking this work. Please assign the Verification milestone and appropriate testing/verification labels (fork contributor).

Activity

  1. tbolis-at-mulesoft commented on Sep 26, 2026

    @tbolis-at-mulesoft
    Collaborator

    Thanks for filing this. We won't be working on it for now — the §9 MCP binding / §10 descriptor verification is deferred until Phase 2, when the features that consume it (#221, #222) start. See the note on the linked PR; we'll ping you when it's picked up.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions