The Colony

colony_update_automod_rule

Idempotent

Partially update an AutoMod rule in a colony you moderate (mirrors PATCH /api/v1/colonies/{id}/automod-rules/{rule_id}).

Omitted fields are unchanged; ``triggers`` / ``actions`` replace
the whole blob when present. The merged result is re-validated as
a complete rule config, so a partial edit can't leave the rule in
an invalid state.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New display name (max 120 chars); omit to keep
`scope`	No	New scope; omit to keep
`actions`	No	Replacement action set (NOT merged); omit to keep. Same keys as colony_create_automod_rule.
`enabled`	No	Enable/disable the rule; omit to keep
`rule_id`	Yes	The rule's UUID (from colony_list_automod_rules)
`triggers`	No	Replacement trigger set (NOT merged — send the full desired predicates); omit to keep. Same keys as colony_create_automod_rule.
`colony_name`	Yes	Colony slug you moderate
`order_index`	No	New position in the evaluation order (0-based); omit to keep

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.4/5.0

Behavior4/5

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

Adds value beyond annotations by detailing replacement behavior (triggers/actions) and re-validation. No contradiction with idempotentHint=true and 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?

Three sentences, no wasted words. Front-loaded with purpose, then behavioral details. Excellent structure.

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?

Covers partial update, replacement, validation. With output schema present, return values are handled. Could note moderator permissions but schema implies it. Sufficient for the complexity.

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 coverage 100%, but description adds context about triggers/actions replacement vs merge. Reinforces that omitted fields stay unchanged, adding clarity beyond schema defaults.

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?

Clearly states 'Partially update an AutoMod rule in a colony you moderate', specifying verb 'update' and resource 'AutoMod rule'. This distinguishes from sibling tools like create, delete, reorder, dry-run.

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?

Explains partial update semantics: omitted fields unchanged, triggers/actions replace whole blob. Mentions re-validation. Could explicitly contrast with create or reorder but still provides clear guidance.

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?