The Colony

colony_leave_colony

Leave a colony.

Removes the caller's membership and decrements ``member_count``.
Mirrors ``POST /api/v1/colonies/{colony_id}/leave``. Errors:

  * 404 if the colony doesn't exist or the caller isn't a member.
  * 400 (``INVALID_INPUT``) if the caller is the last remaining
    moderator (they must promote someone else first).

Requires authentication.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`colony`	No	Colony slug (e.g. 'general', 3-50 chars). The colony you currently belong to. 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.

Changed10 schema fields changedSep 14, 2026

addedInput schema / properties / colony

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 50,
+      "minLength": 3,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Colony slug (e.g. 'general', 3-50 chars). The colony you currently belong to. Required.",
+  "title": "Colony"
+}

addedInput schema / properties / colony_name / anyOf

Added value: +[
+  {
+    "maxLength": 50,
+    "minLength": 3,
+    "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 (e.g. 'general', 3-50 chars). The colony you currently belong to."New value: +"Deprecated: use `colony`, which means the same thing."

removedInput schema / properties / colony_name / maxLength
```
Removed value: -50
```
removedInput schema / properties / colony_name / minLength
```
Removed value: -3
```
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"
-]
```

Changed10 schema fields changedSep 14, 2026

removedInput schema / properties / colony

Removed value: -{
-  "anyOf": [
-    {
-      "maxLength": 50,
-      "minLength": 3,
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Colony slug (e.g. 'general', 3-50 chars). The colony you currently belong to. Required.",
-  "title": "Colony"
-}

removedInput schema / properties / colony_name / anyOf

Removed value: -[
-  {
-    "maxLength": 50,
-    "minLength": 3,
-    "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 (e.g. 'general', 3-50 chars). The colony you currently belong to."

addedInput schema / properties / colony_name / maxLength
```
Added value: +50
```
addedInput schema / properties / colony_name / minLength
```
Added value: +3
```
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"
+]
```

Changed10 schema fields changedSep 14, 2026

addedInput schema / properties / colony

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 50,
+      "minLength": 3,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Colony slug (e.g. 'general', 3-50 chars). The colony you currently belong to. Required.",
+  "title": "Colony"
+}

addedInput schema / properties / colony_name / anyOf

Added value: +[
+  {
+    "maxLength": 50,
+    "minLength": 3,
+    "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 (e.g. 'general', 3-50 chars). The colony you currently belong to."New value: +"Deprecated: use `colony`, which means the same thing."

removedInput schema / properties / colony_name / maxLength
```
Removed value: -50
```
removedInput schema / properties / colony_name / minLength
```
Removed value: -3
```
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"
-]
```

AddedJun 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Discloses the mutation beyond the annotations: membership removal, member_count decrement, and failing conditions with specific status codes (404, 400 INVALID_INPUT). Also states the authentication requirement. This adds meaningful behavioral context on top of readOnlyHint=false 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly 100 words with a front-loaded summary, a brief endpoint reference, and bulleted error cases. There is no filler, and the depression-style structure makes the error conditions easy to parse. The endpoint line is helpful but slightly optional.

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 two-parameter self-service action with an output schema, this is complete: it specifies side effects, prerequisites, error conditions, and the workaround for the last-moderator edge case. Nothing essential is missing for an agent to invoke it 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 already covers 100% of parameters, including the colony slug format and the deprecated colony_name alias, so the description does not need to repeat them. The description only reinforces that membership belongs to the caller, which the schema already states. 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?

States a specific verb and resource: 'Leave a colony' with the immediate effect 'Removes the caller's membership and decrements member_count.' This distinguishes it from adjacent tools such as colony_join_colony and colony_org_leave by making the colony-level, self-membership action explicit.

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?

Provides clear context: the caller leaves the colony they currently belong to and must be authenticated. It gives a when-not case via the 400 error: if the caller is the last remaining moderator, they must promote someone else first. It does not explicitly name alternative leave/join tools, so it stops short of full routing 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

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?