List all available tenants in the federation. Returns tenant IDs, names, and status. Use this to discover which tenants you can interact with. Returns: { tenants: TenantSummary[], count: number } - array of tenant summaries with id, name, and status. Example: call federation_list_tenants 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, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context by detailing the return structure (tenants array with id, name, status) and confirming no arguments are needed, going beyond the annotation-only information.
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, with the primary action front-loaded, followed by the return type, usage guidance, and an example. Every sentence adds value and there is no redundancy.
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?
For a zero-parameter, read-only list tool with strong annotations, the description covers purpose, return structure, and usage example. No output schema exists, but the inline return type is sufficient. The tool is simple enough that no additional context is needed.
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, making schema coverage trivially complete. The description reinforces this with an example showing 'arguments {}', which is helpful despite the schema already indicating no properties. No additional meaning needed.
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 clearly states the tool lists all available tenants in the federation and specifies the return fields (IDs, names, status). This distinguishes it from sibling tools like federation_create_tenant or federation_delete_tenant, which involve mutations.
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 says 'Use this to discover which tenants you can interact with,' providing a clear use case. It doesn't explicitly mention alternatives or when not to use, but the purpose is unambiguous for a listing operation.
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.
