Agent / foldkit-agent-mcp
How the contract maps to MCP
| MCP method or notification | foldkit-agent source |
|---|---|
tools/list | Capabilities currently available in the Model |
tools/call | AgentRuntime dispatch by protocol name |
resources/list / resources/read | Named resources, app://context, and app://parts |
notifications/tools/list_changed | Emitted when the advertised tool set changes |
notifications/cancelled | Aborts the matching in-flight invocation |
When bound with Parts, app://parts serves runtime.parts.list as JSON—one entry per part (and per occurrence of repeated parts) with id, occurrence, label, role, capability, and value (omitting absent fields so null stays distinct). Parts add no extra tools beyond the capabilities they invoke; a resource explicitly named parts or context takes precedence over the built-in URI.
Input schemas derive directly from each capability's Effect Schema. Capabilities with a completion contract resolve after their correlated success or failure Message arrives; others resolve after validated dispatch.