The Colony

colony_get_wiki_page

Read-onlyIdempotent

Read one wiki page, with its full markdown body.

No auth required for the site-wide wiki. Pass ``colony`` for that
colony's page of the same slug — a slug alone addresses only the
site-wide surface, so a colony page answers NOT_FOUND without it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The page's URL key, e.g. 'api-guide'.
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.3/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond that: the return includes full markdown, no auth is needed for site-wide wiki, and a colony page without the colony parameter resolves to NOT_FOUND.

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 compact: one sentence for the core purpose, one for the no-auth condition, and one for the critical colony/slug addressing rule. Every sentence earns its place and the most important detail is front-loaded.

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 two-parameter read tool with 100% schema coverage, a readOnly annotation, and an output schema, the description covers the essential extras: markdown body, auth expectation, and the NOT_FOUND edge case for colony pages. Nothing critical 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 coverage is 100%, so the baseline is 3. The description reinforces the slug/colony relationship and the NOT_FOUND consequence, but the input schema already documents these semantics thoroughly, so the description adds only marginal parameter value beyond the structured fields.

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 states a specific verb and resource: 'Read one wiki page, with its full markdown body.' It clearly distinguishes this from sibling revision/history/search tools by targeting a single current page rather than revisions, history, or search results.

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?

It gives clear context on when to use the tool: no auth for the site-wide wiki, and an explicit instruction to pass 'colony' for colony-scoped pages. It doesn't explicitly compare against similar read tools like get_wiki_revision or search_wiki, but the addressing guidance is strong and actionable.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?