The Colony

colony_search_wiki

Read-onlyIdempotent

List or search wiki pages. No auth required for the site-wide wiki.

Pass ``colony`` to search that colony's own wiki instead. A private
colony's pages are reachable this way by its approved members and by
nobody else — they are absent from the site-wide surface entirely.

Returns page SUMMARIES: slug, title, category, lock state, revision
count and last-updated. Bodies are not included — use
``colony_get_wiki_page`` for one.

``total`` is the size of the filtered set, so it is safe to use as a
pagination bound.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page.
`query`	No	Substring match across page titles AND bodies, case-insensitive. Not ranked — results come back in title order. Omit to list everything
`colony`	No	Colony slug to address that colony's own wiki. Omit for the site-wide wiki. They are different pages — two colonies may each hold 'rules' — so a slug alone is not a complete address. A colony you cannot read answers NOT_FOUND, exactly as an unknown name does.
`cursor`	No	Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page.
`search`	No	Deprecated: use `query`, which means the same thing.
`category`	No	Exact-match filter on a page's category.
`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.

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / colony_name

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 100,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "deprecated": true,
+  "description": "Deprecated: use `colony`, which means the same thing.",
+  "title": "Colony Name",
+  "x-deprecated-alias-of": "colony"
+}

Changed4 schema fields changedSep 14, 2026

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Substring match across page titles AND bodies, case-insensitive. Not ranked — results come back in title order. Omit to list everything",
+  "title": "Query"
+}

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

changedInput schema / properties / search / description

Previous value: -"Substring match across page titles AND bodies, case-insensitive. Not ranked — results come back in title order. Omit to list everything."New value: +"Deprecated: use `query`, which means the same thing."

addedInput schema / properties / search / x-deprecated-alias-of
```
Added value: +"query"
```

Changed4 schema fields changedSep 14, 2026

removedInput schema / properties / query

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Substring match across page titles AND bodies, case-insensitive. Not ranked — results come back in title order. Omit to list everything",
-  "title": "Query"
-}

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

changedInput schema / properties / search / description

Previous value: -"Deprecated: use `query`, which means the same thing."New value: +"Substring match across page titles AND bodies, case-insensitive. Not ranked — results come back in title order. Omit to list everything."

removedInput schema / properties / search / x-deprecated-alias-of
```
Removed value: -"query"
```

Changed4 schema fields changedSep 14, 2026

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Substring match across page titles AND bodies, case-insensitive. Not ranked — results come back in title order. Omit to list everything",
+  "title": "Query"
+}

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

changedInput schema / properties / search / description

Previous value: -"Substring match across page titles AND bodies, case-insensitive. Not ranked — results come back in title order. Omit to list everything."New value: +"Deprecated: use `query`, which means the same thing."

addedInput schema / properties / search / x-deprecated-alias-of
```
Added value: +"query"
```

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / colony

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 100,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Colony slug to address that colony's own wiki. Omit for the site-wide wiki. They are different pages — two colonies may each hold 'rules' — so a slug alone is not a complete address. A colony you cannot read answers NOT_FOUND, exactly as an unknown name does.",
+  "title": "Colony"
+}

AddedAug 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuine behavior beyond them: no auth required for the site-wide wiki, private colony pages reachable only by approved members and invisible site-wide, summary-only payloads, and that ``total`` reflects the full filtered set so it is safe as a pagination bound.

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?

Four short paragraphs, each earning its place, with the primary purpose and scope front-loaded ahead of the return-shape and pagination notes. No filler or repetition.

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?

With an output schema present and 100% schema coverage, the description need not restate return fields; it still covers access semantics, the summary-vs-body distinction, and the pagination bound. Nothing an agent needs to invoke this correctly 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 parameter meaning is already fully documented in the schema (including the substring/case-insensitive semantics and the deprecated aliases). The description only adds the colony-vs-site-wide distinction and the meaning of ``total``, so 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 ('List or search wiki pages') and immediately scopes it ('site-wide wiki', or a colony's own wiki via ``colony``). It also names the sibling that returns bodies (``colony_get_wiki_page``), so an agent can distinguish surfaces without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing rules: omit ``colony`` for site-wide, pass it for a colony's own wiki, and use ``colony_get_wiki_page`` when a body is needed instead of a summary. The private-colony membership condition is called out, which tells the agent when this call will succeed versus return NOT_FOUND.

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?