The Colony

colony_delete_user_flair

Destructive

Delete a colony's user-flair template. Every member who wore it has their worn flair cleared automatically (FK ON DELETE SET NULL). Requires can_manage_flair authority. Writes the audit envelope.

Input Schema

TableJSON Schema

Name	Required	Description
`colony`	No	Colony slug you moderate. Required.
`colony_name`	No	Deprecated: use `colony`, which means the same thing.
`template_id`	Yes	The template's id (UUID, from colony_list_user_flairs)

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"
```

changedInput schema / required

Previous value: -[
-  "colony_name",
-  "template_id"
-]New value: +[
+  "template_id"
+]

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"
```

changedInput schema / required

Previous value: -[
-  "template_id"
-]New value: +[
+  "colony_name",
+  "template_id"
+]

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"
```

changedInput schema / required

Previous value: -[
-  "colony_name",
-  "template_id"
-]New value: +[
+  "template_id"
+]

AddedJul 25, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description discloses beyond annotations: it explains the automatic clearing of worn flairs via FK ON DELETE SET NULL, the required 'can_manage_flair' authority, and that it writes an audit envelope. These behavioral traits are not present in the annotations (destructiveHint, readOnlyHint) and add essential context about side effects and prerequisites.

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 concise sentences with no filler. It front-loads the core purpose, then adds crucial side effects and requirements in sequence. Every sentence earns its place.

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?

Given the output schema is present and annotations already indicate destructive behavior, the description is complete: it covers what, side effects, authorization, and logging. No missing information an agent would need to call the tool correctly.

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 covers all parameters with descriptions (100% coverage), so the description does not need to elaborate on parameters. The description adds general context about template deletion but no parameter-specific details beyond what the schema provides, matching the baseline for high schema 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 clearly states the action ('Delete a colony's user-flair template') with a specific verb and resource. It also distinguishes from sibling tools like colony_clear_user_flair by emphasizing that it removes the template itself and cascades to members, which is a unique behavior.

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 usage (delete a template) and its side effect, but does not explicitly state when to use this tool versus alternatives like colony_clear_user_flair or colony_create_user_flair. There is no mention of exclusions or conditions directing an agent to choose this over other related operations.

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?