federation_help
Get usage instructions for the MCP federation. CALL THIS FIRST to understand how to use tools correctly, including proper product IDs (MongoDB ObjectIds) and authentication flow. Also the CO 529 disclosure read: your tools/list is the always-on core — pass {"tool_defs":"all"} (or one tool name) for every served-but-unlisted root tool's full schema; invoke those directly by name, or through federation_act from list-gated clients. With tenant_id (CO 721), tool_defs answers that tenant's platform tools instead: one name, several as "a,b", or "all". The guide's Prompts section covers the governed prompt library — there's a prompt for that: search it with introspection_prompt_library, run one with federation_prompt_run. Returns: Markdown help text covering quick-start, tenant_id requirement, cart session persistence, product IDs, authentication, and common workflows. Example: call federation_help with arguments {}.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "federation_help"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tenant_id | No | With tool_defs: answer this tenant's platform tool definitions (input_schema, annotations, contract) instead of the root tools'. No token needed. | |
| tool_defs | No | Tool definitions on request. Without tenant_id (CO 529): "all" returns every served-but-unlisted root tool's full def (name, description, input_schema, required_scope, annotations); a tool name returns that one def. With tenant_id (CO 721): the same for that tenant's platform tools, the names in federation_enter_tenant's platform_tools: one name, several as "a,b,c" (at most 25), or "all". Omit for the usage guide. |