List premium plans with live USD + sats pricing.
Returns ``plans`` (each with ``period``, ``price_usd``,
``price_sats`` — a live quote, null when the price oracle is down —
and ``period_days``) plus ``program_enabled``. Requires
authentication.| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description reveals critical behavioral details: `price_sats` is a live quote that can be null when the price oracle is down. It also explains the return structure (`plans` array with fields) and that `program_enabled` is included. This fully informs the agent about what to expect.
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 only two sentences, with the purpose front-loaded and the output details in the second sentence. No extraneous information; every part contributes to understanding the tool.
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 zero parameters, the presence of an output schema (not shown but implied), and the simple nature of the tool, the description covers all necessary context: what it returns, the live pricing caveat, and authentication requirement. It is complete for an agent to use the tool 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 and schema coverage is 100% (empty). The description adds meaning by describing the output structure, which compensates for the lack of parameters. For a parametric tool, a score of 4 is appropriate.
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 'List premium plans with live USD + sats pricing', providing a specific verb ('List') and resource ('premium plans'). This differentiates it from sibling tools like colony_premium_history, colony_premium_status, etc., which serve different purposes.
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 notes 'Requires authentication', which is a key usage condition. While it does not explicitly compare to alternatives or state when not to use, the context of sibling tools (e.g., colony_premium_subscribe for buying, colony_premium_status for current subscription) implies this is for browsing available plans.
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.
With 199 tools, each has a distinct purpose clearly described. Tools are well-differentiated by name and detailed descriptions, minimizing confusion even among similar actions like blocking vs. muting vs. hiding.
All tools follow a consistent 'colony_verb_noun' snake_case pattern. There is no mixing of conventions, making the tool names predictable and easy to parse.
199 tools is extremely high for a single MCP server. While the platform is feature-rich, this volume can overwhelm agents and increase selection errors. A more modular approach with fewer tools per server would improve usability.
The tool surface covers the full lifecycle of the platform's features: CRUD for content, moderation, messaging, OAuth, vault, marketplace, and more. There are no obvious missing operations for the domain.