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. 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 {}.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint true, destructiveHint false, and idempotentHint true, covering its safe read-only nature. The description adds value by specifying it returns Markdown help text and listing the exact topics covered (quick-start, tenant_id requirement, cart session persistence, product IDs, authentication, workflows). No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise—two sentences plus an example—and front-loaded with the critical directive 'CALL THIS FIRST'. Every sentence earns its place: what it does, why to call it first, what it returns, and an example. No fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's trivial complexity (no params, no output schema, no nested objects) and rich annotations, the description is fully complete. It covers the purpose, usage directive, return type, content coverage, and an example. There is nothing missing for an agent to use it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema offers no semantics. The description compensates by providing an example call with empty arguments {} and implicitly clarifying no parameters are needed. This meets the baseline of 4 for no-parameter tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and resource ('usage instructions for the MCP federation'), clearly stating its function. It distinguishes itself from sibling tools by being the introductory/usage guide for the federation, explicitly marked as 'CALL THIS FIRST'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly instructs the agent to call this tool first ('CALL THIS FIRST') and explains why: to understand product IDs and authentication flow. It provides clear context on when to use, effectively making it the entry point for the federation toolset.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is overlap among introspection tools (introspection_system_probe vs. introspection_system_confidence vs. introspection_system_diff) and between similar reading tools (federation_canon_get vs. federation_tenant_info). Descriptions help clarify but boundaries are not always crisp.
Naming is inconsistent: some tools use verb_noun (federation_bond_post, federation_bond_release), some use noun_verb (federation_arena, federation_help), and some use noun_noun (about_us_about, moltbook_read). There are also tools with dot separators (about_us_about) and camelCase (cohort_email_send) mixed with snake_case, making patterns unpredictable.
With 72 tools, the surface is extremely large and likely to overwhelm agents. While the server covers a complex federation platform, this many tools suggest poor scoping or lack of consolidation, making it hard for agents to discover and choose the right tool.
The server covers core federation lifecycle (create/list/update/delete tenants, manage managers, bonds, keys) and some platform operations, but there are gaps such as missing tenant deletion workflow details, no explicit tool for updating manager info, and no direct tool for tenant-level settings beyond basic update. The introspection suite is thorough but the domain may not be evenly covered.
