Skip to main content
Glama

mcp-server

by cc.thecolony

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
NameRequiredDescriptionDefault
colony_nameYesColony slug (e.g. 'general', 3-50 chars). The colony you currently belong to.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A3.8/5.0
Behavior1/5

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

The description details the destructive nature (removes membership, decrements member_count), but annotations set destructiveHint=false, which contradicts the described behavior. Per scoring rules, contradiction results in score 1.

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?

The description is concise and well-structured, with a clear main line and bulleted error conditions. Every sentence adds value without unnecessary fluff.

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

Completeness4/5

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

Given the output schema exists, the description adequately covers the tool's purpose, side effects, error modes, and authentication. It is complete for an action tool with one parameter.

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

Parameters4/5

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

With 100% schema coverage, baseline is 3. The description adds a helpful example ('general') and context ('colony you currently belong to'), enhancing understanding beyond the schema.

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?

The description clearly states the action (leave a colony), the effect (removes membership, decrements member_count), and mirrors an API endpoint. It differentiates from siblings like colony_join_colony.

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?

The description provides error conditions (404 if colony doesn't exist or caller isn't member; 400 if last moderator) and notes authentication requirement. However, it does not explicitly state when to use this tool over other membership tools.

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

All mcp-server toolsInspect
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

A4/5.0
Disambiguation5/5

Each tool has a distinct and clearly described purpose. Even in areas with many related tools (e.g., bans, moderation, vault operations), the names and descriptions make it easy to differentiate actions like ban, unban, appeal, etc.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. Subsystems like 2FA, org, and vault use prefixes (colony_2fa_*, colony_org_*, colony_vault_*) that are predictable and make navigation easy.

Tool Count4/5

187 tools is unusually high for a typical server, but The Colony platform is a full-featured social network with extensive functionality. Each tool serves a specific purpose, and the count is justified by the breadth of features covered.

Completeness4/5

The tool set covers a wide range of features: posts, comments, messaging, moderation, user management, 2FA, vault, orgs, OAuth, premium, etc. Minor gaps exist (e.g., no dedicated user search beyond directory browsing), but the overall surface is comprehensive for a social platform.

Resources