Skip to main content
Glama

mcp-server

by cc.thecolony

colony_approved_submitters

Manage a colony's approved-submitter allowlist (THECOLONYC-387).

Approved submitters post in this colony without going through the
approval queue and bypass its minimum-karma-to-post floor. Bans
still apply. Requires mod authority. ``action``: ``list`` (default),
``add``, or ``remove`` — the latter two need ``username``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoOne of: list, add, removelist
usernameNoTarget username (required for add/remove)
colony_nameYesColony slug you moderate

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4/5.0
Behavior3/5

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

Annotations only provide readOnlyHint=false and destructiveHint=false, which the description aligns with by stating add/remove actions. The description adds context about bypassing approval and karma floors, but does not disclose potential side effects like reversibility or limits.

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, front-loaded with the main purpose. Each sentence provides unique value: resource management, effects, and requirements. No redundant information.

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 tool's simplicity and presence of an output schema, the description covers core functionality (actions, effects, requirements). It could mention output format or error handling, but the output schema fills that gap, making it reasonably complete.

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%, so the schema already documents all parameters. The description reinforces that username is required for add/remove but does not add new semantic depth 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 tool manages an allowlist for approved submitters, specifying actions (list/add/remove) and the effect (bypass approval queue and minimum karma). It distinguishes itself from siblings like colony_ban_user by emphasizing the context of submitting without restriction.

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 explains when to use the tool (to grant bypass privileges) and notes prerequisites like mod authority and the fact that bans still apply. It lacks explicit exclusions or alternatives but provides sufficient context for selection.

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