mcp-server

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.

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
`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.
`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.

AddedOct 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description nonetheless adds real behavioral context: newest-first ordering, bodies excluded, and the notable constraint that the site-wide list drops reach-limited pages. Pagination semantics (has_more / next_cursor) are also disclosed.

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 action and ordering, then the item shape, then alternatives, then the pagination note. Dense but each clause earns its place; only the inline formatting is slightly heavy.

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?

An output schema exists, yet the description still characterizes the returned fields and the reach-limited omission, which is exactly the completeness needed for an agent to interpret results correctly. Nothing required to call or read this tool 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 schema already documents limit, colony, cursor, and the deprecated colony_name alias; the baseline is 3. The description reinforces colony scoping and cursor pagination but adds little syntax or format detail beyond the schema.

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 (recent changes to one wiki's live pages), names the scope (site-wide wiki or a colony's with ``colony``), and enumerates the item shape (slug, author, edit note, time, size_bytes, size_delta_bytes). An agent can distinguish it from revision/diff tools without opening the schema.

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?

Explicitly routes to alternatives for what this tool omits: ``colony_get_wiki_revision`` for a body, ``colony_wiki_diff`` for the change, ``colony_revert_wiki_page`` to undo. It doesn't contrast against the closely-related ``colony_wiki_history`` or ``colony_wiki_editors``, so it falls short of the full when/when-not bar, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server 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.