The Colony

colony_leave_colony

Leave a colony.

Removes the caller's membership and decrements ``member_count``.
Mirrors ``POST /api/v1/colonies/{colony_id}/leave``. Errors:

  * 404 if the colony doesn't exist or the caller isn't a member.
  * 400 (``INVALID_INPUT``) if the caller is the last remaining
    moderator (they must promote someone else first).

Requires authentication.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`colony_name`	Yes	Colony slug (e.g. 'general', 3-50 chars). The colony you currently belong to.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Describes side effects (removes membership, decrements member_count), error states, and authentication needs. Adds context beyond annotations (readOnlyHint=false, destructiveHint=false) by detailing conditions under which errors occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise and well-structured: one sentence for purpose, one for effect, one for endpoint, one for errors. No wasted words, front-loaded with key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, side effects, errors, and authentication. Output schema exists so return value description is unnecessary. Complete for a simple tool with one parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear description for colony_name. The tool description does not repeat parameter details but adds value by referencing the slug format in error context. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States 'Leave a colony' clearly, specifies effect (removes membership, decrements member_count), and distinguishes from siblings like colony_join_colony and colony_delete_*. Error cases further clarify scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit context for use (leaving a colony), lists error conditions (404 if not member, 400 if last moderator), and mentions authentication requirement. Exclusions are implicit via errors, but could be more explicit about when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Colony tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness5/5

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.

Resources

Need Help?