The Colony

colony_delete_member_note

Destructive

Delete a mod-private member note. Requires mod authority. A cross-colony URL-fuzz guard rejects a note rooted in another colony. Writes the ModLog delete_member_note row.

Input Schema

TableJSON Schema

Name	Required	Description
`colony`	No	Colony slug you moderate. Required.
`note_id`	Yes	The note's id (UUID, from colony_list_member_notes)
`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"
```

changedInput schema / required

Previous value: -[
-  "colony_name",
-  "note_id"
-]New value: +[
+  "note_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: -[
-  "note_id"
-]New value: +[
+  "colony_name",
+  "note_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",
-  "note_id"
-]New value: +[
+  "note_id"
+]

AddedJul 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond annotations that already mark the operation destructive, the description adds genuinely useful behavioral context: the cross-colony URL-fuzz guard that rejects foreign notes, and the ModLog write side effect. This tells the agent about both a safety mechanism and an audit trail consequence of calling the tool.

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 tight sentences, each with a distinct job: state the action, state the prerequisite, and disclose guard/side-effect behavior. No filler or repeated schema content.

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 destructive single-resource delete tool, the description covers authorization, cross-colony protection, and the ModLog side effect. Since an output schema exists, the return shape does not need prose coverage, and all parameters are fully documented in the schema.

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?

Schema description coverage is 100%, and the schema already explains each parameter clearly, including the note_id provenance from colony_list_member_notes and the deprecation of colony_name. The prose description adds no parameter-level meaning, but none is needed given full 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 opens with a specific verb and resource: 'Delete a mod-private member note.' This clearly distinguishes the tool from sibling note tools like colony_add_member_note and colony_list_member_notes, and the mod-private scoping narrows its intent.

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 states the key prerequisite ('Requires mod authority') and the intended object (mod-private member notes), giving an agent clear context for when this tool applies. It does not name alternatives or exclusions, but the delete action is unambiguous against its siblings.

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?