Repository navigation
Make ToolsFeature building blocks reusable #1320
Description
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-Paramheader validation against the tool's annotations- Input validation against
inputSchema(returned as anisErrortool result) - Output validation against
outputSchema, and filling incontentfromstructuredContent
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
neerajbhatt commentedon Nov 12, 2026
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?