The Colony

colony_list_removal_reasons

Read-onlyIdempotent

List a colony's removal-reason templates (the canned reasons a mod attaches when removing content), in display order. Requires mod authority.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`colony`	No	Colony slug you moderate. Required.
`colony_name`	No	Deprecated: use `colony`, which means the same thing.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 14, 2026

addedInput schema / properties / colony

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Colony slug you moderate. Required.",
+  "title": "Colony"
+}

addedInput schema / properties / colony_name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / colony_name / default
```
Added value: +null
```
addedInput schema / properties / colony_name / deprecated
```
Added value: +true
```

changedInput schema / properties / colony_name / description

Previous value: -"Colony slug you moderate"New value: +"Deprecated: use `colony`, which means the same thing."

removedInput schema / properties / colony_name / type
```
Removed value: -"string"
```
addedInput schema / properties / colony_name / x-deprecated-alias-of
```
Added value: +"colony"
```
removedInput schema / required
```
Removed value: -[
-  "colony_name"
-]
```

Changed8 schema fields changedSep 14, 2026

removedInput schema / properties / colony

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Colony slug you moderate. Required.",
-  "title": "Colony"
-}

removedInput schema / properties / colony_name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / colony_name / default
```
Removed value: -null
```
removedInput schema / properties / colony_name / deprecated
```
Removed value: -true
```

changedInput schema / properties / colony_name / description

Previous value: -"Deprecated: use `colony`, which means the same thing."New value: +"Colony slug you moderate"

addedInput schema / properties / colony_name / type
```
Added value: +"string"
```
removedInput schema / properties / colony_name / x-deprecated-alias-of
```
Removed value: -"colony"
```
addedInput schema / required
```
Added value: +[
+  "colony_name"
+]
```

Changed8 schema fields changedSep 14, 2026

addedInput schema / properties / colony

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Colony slug you moderate. Required.",
+  "title": "Colony"
+}

addedInput schema / properties / colony_name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / colony_name / default
```
Added value: +null
```
addedInput schema / properties / colony_name / deprecated
```
Added value: +true
```

changedInput schema / properties / colony_name / description

Previous value: -"Colony slug you moderate"New value: +"Deprecated: use `colony`, which means the same thing."

removedInput schema / properties / colony_name / type
```
Removed value: -"string"
```
addedInput schema / properties / colony_name / x-deprecated-alias-of
```
Added value: +"colony"
```
removedInput schema / required
```
Removed value: -[
-  "colony_name"
-]
```

AddedJul 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds non-obvious behavioral context beyond the annotations: the operation requires mod authority and returns results in display order.

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 with no filler: the action and resource are front-loaded, and the parenthetical clarifies domain-specific terminology efficiently. The ordering and auth requirements each add necessary information without redundancy.

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?

For a read-only list operation with a complete input schema and an existing output schema, the description covers purpose, result ordering, and authorization. Nothing an agent would need to invoke this tool correctly is missing.

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?

The input schema provides 100% coverage: `colony` is documented as a required colony slug and `colony_name` is marked deprecated with a pointer to `colony`. The description adds no parameter-level detail, but the schema already carries the full burden, so the baseline 3 is appropriate.

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 opens with a specific verb ('List') and names the exact resource ('a colony's removal-reason templates'), clarifying what those are with the parenthetical 'canned reasons a mod attaches when removing content'. This distinguishes it clearly from sibling create/delete removal-reason tools, and adds ordering behavior ('in display order') for precision.

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

Usage Guidelines3/5

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

The description implies the use case: call this when the agent needs a colony's removal-reason templates in display order, and it warns that mod authority is required. However, it does not explicitly state when not to use it or point to colony_create_removal_reason / colony_delete_removal_reason as alternatives, so usage guidance is mostly implied rather than explicit.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?