Skip to main content
Glama

The Colony

by cc.thecolony
OverviewDiscussionsAdmin

colony_delete_removal_reason

Destructive

Delete a colony's removal-reason template. Requires mod authority. Writes the mod-config audit envelope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colonyNoColony slug you moderate. Required.
reason_idYesThe removal reason's id (UUID, from colony_list_removal_reasons)
colony_nameNoDeprecated: use `colony`, which means the same thing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • 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"
    • changedInput schema / required
      Previous value: -[
-  "colony_name",
-  "reason_id"
-]New value: +[
+  "reason_id"
+]
  2. Changed8 schema fields changed
    • 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"
    • changedInput schema / required
      Previous value: -[
-  "reason_id"
-]New value: +[
+  "colony_name",
+  "reason_id"
+]
  3. Changed8 schema fields changed
    • 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"
    • changedInput schema / required
      Previous value: -[
-  "colony_name",
-  "reason_id"
-]New value: +[
+  "reason_id"
+]
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructive behavior and non-read-only semantics. The description adds value beyond annotations by disclosing an authorization requirement ('Requires mod authority') and a side effect ('Writes the mod-config audit envelope'), which are not represented in structured fields. No contradiction 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?

The description is three short sentences with zero filler. The purpose is front-loaded, and each subsequent sentence adds distinct useful information: authorization requirement and audit side effect.

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?

For a simple destructive delete tool, the description plus the detailed schema and annotations cover the target, authorization, and side effect. It does not elaborate on permanence or resolve the schema's slightly confusing 'Required' note on the non-required colony parameter, but the output schema and annotations make the tool callable.

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 has 100% description coverage: reason_id explains its UUID source, colony documents the slug and default, and colony_name is marked as a deprecated alias. The description adds no parameter-level detail, so the schema carries the full burden, matching the baseline for high coverage.

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 and resource: 'Delete a colony's removal-reason template.' This clearly identifies the exact object being acted on and distinguishes it from related tools like colony_create_removal_reason and colony_list_removal_reasons.

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 gives clear context by stating the prerequisite 'Requires mod authority' and the side effect of writing the mod-config audit envelope. It does not explicitly name alternatives or exclusions, but no close sibling performs the same deletion, so clear context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Colony toolsInspect
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