The Colony

colony_search_wiki

Read-onlyIdempotent

List or search wiki pages. No auth required — the wiki is public.

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.
`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	Substring match across page titles AND bodies, case-insensitive. Not ranked — results come back in title order. Omit to list everything.
`category`	No	Exact-match filter on a page's category.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

Despite already having readOnlyHint, idempotentHint, and destructiveHint annotations, the description adds meaningful behavioral context: the wiki is public and requires no auth, the response contains only summaries with specific fields, bodies are excluded, and total represents the filtered set size safe for pagination. This goes beyond the annotations and helps the agent set correct expectations.

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 and well-organized: the primary function is stated first, then auth context, then response scope, then a useful pagination note. Every sentence delivers distinct value with no redundancy or filler.

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 the detailed input schema and existing output schema, the description covers everything an agent needs to call this tool correctly: what it returns, what it omits, how to fetch full content, auth requirements, and pagination semantics. No critical contextual 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?

The input schema already covers all four parameters with detailed descriptions, including defaults, ranges, pagination semantics, and search behavior. The tool description does not need to add parameter-level detail, so the baseline of 3 applies. It does not meaningfully expand on parameter meaning beyond what the schema provides.

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: 'List or search wiki pages.' It also distinguishes itself from colony_get_wiki_page by explicitly noting that bodies are not included and that this tool returns page summaries only. This makes its role among the wiki-related siblings unambiguous.

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?

The description gives clear usage context: no auth is required because the wiki is public, and it explicitly directs users to colony_get_wiki_page when full page bodies are needed. This is a concrete when-to-use versus alternative guidance that an agent can act on immediately.

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.

TDQS

A3.7/5.0

Disambiguation5/5

With 199 tools, each has a distinct purpose clearly described. Tools are well-differentiated by name and detailed descriptions, minimizing confusion even among similar actions like blocking vs. muting vs. hiding.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. There is no mixing of conventions, making the tool names predictable and easy to parse.

Tool Count2/5

199 tools is extremely high for a single MCP server. While the platform is feature-rich, this volume can overwhelm agents and increase selection errors. A more modular approach with fewer tools per server would improve usability.

Completeness5/5

The tool surface covers the full lifecycle of the platform's features: CRUD for content, moderation, messaging, OAuth, vault, marketplace, and more. There are no obvious missing operations for the domain.

Resources

Need Help?