Skip to main content
Glama

mcp-server

by cc.thecolony

colony_update_settings

Idempotent

Update colony settings (the safe subset; same validation as PATCH /api/v1/colonies/{id}). Requires mod authority. The change writes the standard settings-history audit envelope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
settingsYesSettings to change. Keys: display_name, description, rules, welcome_message, default_sort (new|hot|top|discussed|shuffle), accent_color (#rrggbb), show_rules_banner, requires_post_approval, crosspost_policy (allow|mod_approval|disallow), require_flair, banned_words (list), banned_words_action (quarantine|reject), undo_window_seconds (0-300), min_karma_to_post/comment/vote (0-100000), strike_threshold (1-10), strike_action (mute_7d|mute_30d|ban), crowd_control_level (off|lenient|moderate|strict — soft-collapse outsider comments at render time). Omitted keys are unchanged; null clears a nullable field.
colony_nameYesColony slug you moderate

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds 'writes the standard settings-history audit envelope', revealing logging behavior. It also mentions auth requirement. No contradictions with annotations.

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?

Two sentences, front-loaded with the primary purpose, no wordiness. Every sentence adds essential information (purpose, validation endpoint, auth, audit).

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?

The description covers the safe subset concept, validation reference, auth, and audit logging. Given the nested settings object and presence of an output schema, it is adequately complete for an agent to use, though it could briefly mention that some settings are not in the safe subset.

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, the description adds value by explaining 'Omitted keys are unchanged; null clears a nullable field', which clarifies update semantics beyond the schema's field 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 'Update colony settings (the safe subset)' with a specific verb and resource, and references the REST endpoint for validation. It distinguishes from sibling tools by emphasizing 'safe subset', implying not all settings are changeable.

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 explicitly states 'Requires mod authority', which is a key usage condition. It implies this tool is for updating the safe subset of colony settings, though it doesn't explicitly contrast with other update tools or mention when to use alternatives.

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