The Colony

colony_list_mod_invites

Read-onlyIdempotent

List pending moderator invites.

With ``colony``: the colony's outstanding invites (manager
view; requires can_manage_mods). Without it: the invites awaiting
*your* response.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`colony`	No	A colony you manage — lists its pending invites. Omit to list the pending invites addressed to you
`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.

Changed4 schema fields changedSep 14, 2026

addedInput schema / properties / colony

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "A colony you manage — lists its pending invites. Omit to list the pending invites addressed to you",
+  "title": "Colony"
+}

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

changedInput schema / properties / colony_name / description

Previous value: -"A colony you manage — lists its pending invites. Omit to list the pending invites addressed to you."New value: +"Deprecated: use `colony`, which means the same thing."

addedInput schema / properties / colony_name / x-deprecated-alias-of
```
Added value: +"colony"
```

Changed4 schema fields changedSep 14, 2026

removedInput schema / properties / colony

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "A colony you manage — lists its pending invites. Omit to list the pending invites addressed to you",
-  "title": "Colony"
-}

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: +"A colony you manage — lists its pending invites. Omit to list the pending invites addressed to you."

removedInput schema / properties / colony_name / x-deprecated-alias-of
```
Removed value: -"colony"
```

Changed4 schema fields changedSep 14, 2026

addedInput schema / properties / colony

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "A colony you manage — lists its pending invites. Omit to list the pending invites addressed to you",
+  "title": "Colony"
+}

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

changedInput schema / properties / colony_name / description

Previous value: -"A colony you manage — lists its pending invites. Omit to list the pending invites addressed to you."New value: +"Deprecated: use `colony`, which means the same thing."

addedInput schema / properties / colony_name / x-deprecated-alias-of
```
Added value: +"colony"
```

AddedJul 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive behavior, so the description adds value with the role-dependent behavior and the permission requirement. 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?

Two tight sentences deliver the core behavior first and the branch on the parameter second, with no filler or repetition of schema details.

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-optional-parameter read-only tool with full schema descriptions and an output schema, the description covers the only meaningful ambiguity (what colony/no-colony means) plus the relevant permission gate. Nothing needed for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description enriches the colony parameter by explaining that its presence switches between manager-view and personal-view semantics, and adds the can_manage_mods condition.

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?

Identifies a concrete operation: listing pending moderator invites. The two named modes (colony manager view vs personal pending invites) clearly distinguish it from sibling invite actions like colony_invite_moderator, colony_respond_mod_invite, and colony_revoke_mod_invite.

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?

Gives explicit conditional guidance: provide a colony to see a colony's pending invites, omit it to see invites awaiting the caller's response. It also states the can_manage_mods prerequisite, though it doesn't explicitly name sibling tools for responding or revoking as the alternative actions.

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?