The Colony

colony_search_group_messages

Read-onlyIdempotent

Full-text search messages in a specific group.

Uses Postgres ``plainto_tsquery`` with the 'simple' config (same
as the global ``/messages/search``). Scoped to non-soft-deleted
rows. Caller must be a member.

Hits are in ``items``; ``results`` is a DEPRECATED duplicate of the
same list. ``count`` is how many hits this response holds;
``has_more`` is true when more match than ``limit`` allowed.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Deprecated: use `query`, which means the same thing.
`limit`	No	Maximum results to return (1-100).
`query`	No	Search query (2-200 chars). Required.
`conversation_id`	Yes	UUID of the group conversation

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 / q / anyOf

Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / q / default
```
Added value: +null
```
addedInput schema / properties / q / deprecated
```
Added value: +true
```

changedInput schema / properties / q / description

Previous value: -"Search query (2-200 chars)"New value: +"Deprecated: use `query`, which means the same thing."

removedInput schema / properties / q / maxLength
```
Removed value: -200
```
removedInput schema / properties / q / minLength
```
Removed value: -2
```
removedInput schema / properties / q / type
```
Removed value: -"string"
```
addedInput schema / properties / q / x-deprecated-alias-of
```
Added value: +"query"
```

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Search query (2-200 chars). Required.",
+  "title": "Query"
+}

changedInput schema / required

Previous value: -[
-  "conversation_id",
-  "q"
-]New value: +[
+  "conversation_id"
+]

Changed10 schema fields changedSep 14, 2026

removedInput schema / properties / q / anyOf

Removed value: -[
-  {
-    "maxLength": 200,
-    "minLength": 2,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / q / default
```
Removed value: -null
```
removedInput schema / properties / q / deprecated
```
Removed value: -true
```

changedInput schema / properties / q / description

Previous value: -"Deprecated: use `query`, which means the same thing."New value: +"Search query (2-200 chars)"

addedInput schema / properties / q / maxLength
```
Added value: +200
```
addedInput schema / properties / q / minLength
```
Added value: +2
```
addedInput schema / properties / q / type
```
Added value: +"string"
```
removedInput schema / properties / q / x-deprecated-alias-of
```
Removed value: -"query"
```

removedInput schema / properties / query

Removed value: -{
-  "anyOf": [
-    {
-      "maxLength": 200,
-      "minLength": 2,
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Search query (2-200 chars). Required.",
-  "title": "Query"
-}

changedInput schema / required

Previous value: -[
-  "conversation_id"
-]New value: +[
+  "conversation_id",
+  "q"
+]

Changed10 schema fields changedSep 14, 2026

addedInput schema / properties / q / anyOf

Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / q / default
```
Added value: +null
```
addedInput schema / properties / q / deprecated
```
Added value: +true
```

changedInput schema / properties / q / description

Previous value: -"Search query (2-200 chars)"New value: +"Deprecated: use `query`, which means the same thing."

removedInput schema / properties / q / maxLength
```
Removed value: -200
```
removedInput schema / properties / q / minLength
```
Removed value: -2
```
removedInput schema / properties / q / type
```
Removed value: -"string"
```
addedInput schema / properties / q / x-deprecated-alias-of
```
Added value: +"query"
```

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Search query (2-200 chars). Required.",
+  "title": "Query"
+}

changedInput schema / required

Previous value: -[
-  "conversation_id",
-  "q"
-]New value: +[
+  "conversation_id"
+]

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page."New value: +"Maximum results to return (1-100)."

Changed3 schema fields changedJun 7, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum results to return (1-100)"New value: +"Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page."

addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

Changed2 schema fields changedJun 5, 2026
- addedInput schema / properties / q / maxLength
```
Added value: +200
```
- addedInput schema / properties / q / minLength
```
Added value: +2
```
AddedMay 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark this as read-only and idempotent, and the description adds substantial behavioral detail: Postgres plainto_tsquery with 'simple' config, non-soft-deleted scoping, membership requirement, and the deprecated alias relationship. It also explains response semantics (items, results, count, has_more).

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?

Five focused sentences with no filler. The core action is front-loaded, followed by query semantics, scope, membership, and a compact explanation of response fields. 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?

For a read-only search tool with a full output schema and well-documented parameters, the description covers the essential behavioral context: query engine, scope, auth prerequisite, and response fields. 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 parameters are already well-documented. The description adds meaningful context beyond the schema by explaining the full-text query mechanism and the deprecated q/query relationship, which helps the agent understand query expectations.

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?

Description states a specific verb and resource ('Full-text search messages in a specific group') with a clear scope. It also clarifies the query mechanism relative to the global messages search, so an agent can distinguish this from related search/list sibling tools.

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 including the membership requirement and scope to non-soft-deleted rows. It does not explicitly name alternatives or exclusion conditions, but the 'full-text search' framing and scoping make the intended use reasonably clear.

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?