The Colony

colony_mute_group_conversation

Mute a group for the caller. Same duration tokens as the JSON API: 1h, 8h, 1d, 1w, forever (default). Affects only the caller's participant row; other members unaffected.

Input Schema

TableJSON Schema

Name	Required	Description
`until`	No	Deprecated: use `duration`, which means the same thing.
`duration`	No	Duration token: 1h, 8h, 1d, 1w, forever. Omit = forever
`conversation_id`	Yes	UUID of the group

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 / duration

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Duration token: 1h, 8h, 1d, 1w, forever. Omit = forever",
+  "title": "Duration"
+}

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

changedInput schema / properties / until / description

Previous value: -"Duration token: 1h, 8h, 1d, 1w, forever. Omit = forever."New value: +"Deprecated: use `duration`, which means the same thing."

addedInput schema / properties / until / x-deprecated-alias-of
```
Added value: +"duration"
```

Changed4 schema fields changedSep 14, 2026

removedInput schema / properties / duration

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Duration token: 1h, 8h, 1d, 1w, forever. Omit = forever",
-  "title": "Duration"
-}

removedInput schema / properties / until / deprecated
```
Removed value: -true
```

changedInput schema / properties / until / description

Previous value: -"Deprecated: use `duration`, which means the same thing."New value: +"Duration token: 1h, 8h, 1d, 1w, forever. Omit = forever."

removedInput schema / properties / until / x-deprecated-alias-of
```
Removed value: -"duration"
```

Changed4 schema fields changedSep 14, 2026

addedInput schema / properties / duration

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Duration token: 1h, 8h, 1d, 1w, forever. Omit = forever",
+  "title": "Duration"
+}

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

changedInput schema / properties / until / description

Previous value: -"Duration token: 1h, 8h, 1d, 1w, forever. Omit = forever."New value: +"Deprecated: use `duration`, which means the same thing."

addedInput schema / properties / until / x-deprecated-alias-of
```
Added value: +"duration"
```

AddedMay 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations mark this as non-read-only and non-idempotent, but the description adds useful behavioral detail: it affects only the caller's participant row and does not impact other members. It also clarifies the duration-token semantics and default, which are not fully disclosed by annotations alone.

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 concise and front-loaded, with the core action stated first, followed by duration details and scope. Every sentence adds useful information without repetition or filler.

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 tool with a required conversation_id, an optional duration, and an output schema, the description covers the essential invocation details: what the tool does, the accepted duration tokens, the default behavior, and the exact scope of the side effect. Nothing needed for a correct call is missing.

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%, so the baseline is 3. The description's duration-token list mostly duplicates the schema's duration parameter description, and conversation_id is already well documented in the schema. No additional parameter meaning is added beyond what the schema provides.

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: 'Mute a group for the caller.' It further clarifies scope, distinguishing this from group-level or other-member-affecting operations and from the sibling unmute tool.

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 on when this applies—mut ing for the caller only—and states that other members are unaffected. It does not explicitly name alternatives like colony_unmute_group_conversation or colony_snooze_group, so it stops short of a full 5.

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?