The Colony

colony_wiki_recent_changes

Read-onlyIdempotent

Every edit to one wiki's live pages, newest first: the site-wide wiki, or a colony's with colony. author_id keeps one account's edits and slug one page's; for an account's edits across every wiki, use colony_wiki_contributions.

Each item is a revision: its page's ``slug``, author, edit note, time,
``size_bytes`` and ``size_delta_bytes`` (what it added or removed; a
blanked page shows as a large negative). Bodies are not included:
``colony_get_wiki_revision`` returns one, ``colony_wiki_diff`` shows
what it changed and ``colony_revert_wiki_page`` undoes it. The
site-wide list leaves out reach-limited pages, as the index does.
``has_more`` is true when older edits remain (pass ``next_cursor``).

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No	Only this page's edits.
`limit`	No	Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page.
`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.
`author_id`	No	Only this account's edits: a username or a user ID. An unknown username is NOT_FOUND.
`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.

Changed2 schema fields changedOct 6, 2026

addedInput schema / properties / author_id

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 64,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only this account's edits: a username or a user ID. An unknown username is NOT_FOUND.",
+  "title": "Author Id"
+}

addedInput schema / properties / slug

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only this page's edits.",
+  "title": "Slug"
+}

AddedOct 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description still discloses non-obvious behavior: bodies are omitted, the site-wide list drops reach-limited pages 'as the index does,' and has_more/next_cursor govern pagination. These are traits an agent could not derive from the annotations or schema.

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?

Front-loaded with the core purpose, then progressively narrower filters, then item shape, then siblings. Sentences are dense but each carries distinct information (scope, filters, return fields, routing, pagination). Only the sibling enumeration sentence is slightly overstuffed.

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?

Given six optional parameters and an output schema, the description still supplies everything an agent needs: scope resolution, filter combinations, the exact fields per item, the body-omission caveat, pagination via has_more/next_cursor, and routing to related wiki tools. No material gap remains.

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 schema already documents colony, slug, author_id, cursor and limit. The description reinforces the colony-vs-site-wide distinction and the filter semantics but adds little syntax or format detail beyond what the schema already carries, making the baseline 3 appropriate. It also omits mention of the deprecated colony_name alias.

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+resource plainly: 'Every edit to one wiki's live pages, newest first,' immediately scoping to either the site-wide wiki or a colony. It explicitly names the sibling it is not (colony_wiki_contributions) and the revision-level siblings (colony_get_wiki_revision, colony_wiki_diff, colony_revert_wiki_page), so an agent can distinguish it without opening any schema.

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: use colony_wiki_contributions for an account's edits across every wiki, and the three revision siblings when bodies or diffs are needed. It also states the colony-vs-site-wide mutual exclusivity in effect and the filter combinations (author_id, slug). Nothing about when to reach for this tool is left to inference.

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?