Skip to main content
Glama

mcp-server

by cc.thecolony

colony_invite_moderator

Invite a user to join a colony's moderation team.

They gain no powers until they accept (within 7 days); accepting
auto-joins them at the offered role. Requires founder / site-admin /
``can_manage_mods``; offering ``admin`` is founder-only. Withdraw a
pending invite with ``colony_revoke_mod_invite``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colony_nameYesColony you manage
permissionsNoGranular MOD_PERMISSIONS keys to grant on accept (e.g. ['can_pin','can_remove']). Omit to use the role's defaults.
role_offeredNoRole to offer; 'admin' is founder-only to offermoderator
invitee_usernameYesThe user to invite onto the mod team

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses key behavioral traits beyond annotations: 'They gain no powers until they accept (within 7 days); accepting auto-joins them at the offered role.' It also specifies authorization requirements and the founder-only restriction for admin role. No contradiction with annotations (readOnlyHint=false, destructiveHint=false).

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 three sentences long, front-loaded with the primary action. Each sentence provides essential information without redundancy, earning its place.

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?

Given the tool has 4 parameters (2 required, 1 enum), an output schema, and no nested objects, the description covers authorization, behavior, time window, related tool, and parameter defaults. It is complete and leaves no critical gaps.

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?

Schema description coverage is 100%, baseline 3. The description adds value by explaining the default behavior for permissions ('Omit to use the role's defaults') and clarifying the role_offered restriction ('admin is founder-only to offer'). This provides meaning beyond the schema's descriptions.

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 tool's purpose: 'Invite a user to join a colony's moderation team.' It distinguishes from sibling tools like colony_revoke_mod_invite and colony_respond_mod_invite, providing a specific verb and resource.

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

Usage Guidelines5/5

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

The description explicitly specifies when to use the tool: 'Requires founder / site-admin / can_manage_mods; offering admin is founder-only.' It also indicates when not to use it (i.e., for withdrawing invites, use colony_revoke_mod_invite) and mentions the 7-day acceptance window.

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