GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Make `ToolsFeature` building blocks reusable · Issue #1320 · modelcontextprotocol/java-sdk

Make ToolsFeature building blocks reusable #1320

New issue
Copy link
New issue
Copy link
Open
Enhancement
Open
Make ToolsFeature building blocks reusable#1320
Enhancement
Copy link
Labels
P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable featurearea/servermodernv3 covering the 2026-07-28 specv3 covering the 2026-07-28 spec
Milestone
2.2.0-M3

Description

@Kehrlann
Kehrlann
opened on Nov 9, 2026
Issue body actions

Context

In #1013, the plan is for Tasks (SEP-2663) to be a feature of its own that replaces ToolsFeature entirely instead of wrapping it (comment).

To do that without copying ToolsFeature, the logic it applies around a tools/call needs to be reusable.

Proposal

Pull the per-call steps out of ToolsFeature so that another feature can build on them:

  • Required client capabilities check (RequiredCapabilities.check)
  • Mcp-Param header validation against the tool's annotations
  • Input validation against inputSchema (returned as an isError tool result)
  • Output validation against outputSchema, and filling in content from structuredContent

ToolsFeature should keep working exactly as it does today, built on top of these pieces.

Out of scope

  • The Tasks feature itself (SEP-2663: Tasks Extension #1013)

Activity

  1. Kehrlann
    added this to the 2.2.0-M3 milestone on Nov 9, 2026
  2. Kehrlann
    added the
    Enhancement
    issue type on Nov 9, 2026
  3. Kehrlann
    added
    area/server
    P1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested feature
    P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable feature
    modernv3 covering the 2026-07-28 specv3 covering the 2026-07-28 spec
    and removed
    P1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested feature
    on Nov 9, 2026
  4. neerajbhatt commented on Nov 12, 2026

    @neerajbhatt
    neerajbhatt
    on Nov 12, 2026
    Contributor
    More actions

    Hi @Kehrlann, I’d be interested in working on #1320. I recently raised a PR for #1317. My proposed scope is to make the capability, Mcp-Param, and input/output schema checks in ToolsFeature reusable, with focused tests to preserve its current behavior. I’d leave the Tasks feature itself out of scope. If that aligns with your plan, could you assign this issue to me?

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

    P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable featurearea/servermodernv3 covering the 2026-07-28 specv3 covering the 2026-07-28 spec

    Type

    Enhancement

    Projects

    No projects

      Milestone

      • 2.2.0-M3No due date

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.