Radix Wiki

Whole corpus

get_full_corpus

Read-onlyIdempotent

Every article as one plain-text document, for bulk ingestion rather than reading. PREFLIGHT FIRST: call it with sizeOnly=true for the exact character count, a token estimate and the per-branch breakdown — the whole corpus is several times a context window. Then pull it with maxChars (default 200000, max 1000000), or narrow it with tagPath to take one branch at a time. Truncation is page-aligned and honest: truncated, omittedPages and nextSkip say exactly where to resume (pass skip=nextSkip). Search or list first if you have a question; the same corpus is also served, cacheably and with an ETag, at /llms-full.txt.

Input Schema

TableJSON Schema

Name	Required	Description
`skip`	No	Resume from this page index — pass the `nextSkip` from the previous truncated call (default 0)
`tagPath`	No	Restrict to one branch and its descendants, e.g. "contents/tech". Omit for everything.
`maxChars`	No	Character budget for `document` (default 200000, max 1000000)
`sizeOnly`	No	Return sizes and breakdowns only, no document. Do this before the first real pull.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 6, 2026

addedInput schema / properties / maxChars

Added value: +{
+  "description": "Character budget for `document` (default 200000, max 1000000)",
+  "type": "number"
+}

addedInput schema / properties / sizeOnly

Added value: +{
+  "description": "Return sizes and breakdowns only, no document. Do this before the first real pull.",
+  "type": "boolean"
+}

addedInput schema / properties / skip

Added value: +{
+  "description": "Resume from this page index — pass the `nextSkip` from the previous truncated call (default 0)",
+  "type": "number"
+}

addedInput schema / properties / tagPath

Added value: +{
+  "description": "Restrict to one branch and its descendants, e.g. \"contents/tech\". Omit for everything.",
+  "type": "string"
+}

First observedAug 2, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and closed-world hints, and the description adds significant context beyond that: plain-text format, bulk-ingestion intent, corpus size warning, page-aligned truncation, and honest resume fields (truncated, omittedPages, nextSkip). The description is consistent with annotations and discloses behavior not inferable from schema or hints.

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 dense but every sentence earns its place: purpose, preflight warning, pull strategy, truncation protocol, and alternative access. It is front-loaded with the core use case and uses formatting (PREFLIGHT FIRST, backticks) to make the critical information scannable.

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 read-only bulk retrieval tool with four optional parameters and no output schema, the description fully covers invocation order, parameter limits, pagination and truncation semantics, and even the alternate ETag-served endpoint. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds real value beyond the schema: it explains the preflight-first ordering for sizeOnly, provides the maxChars default and ceiling, gives a concrete tagPath example, and introduces the skip=nextSkip pagination contract. This materially improves an agent's ability to use the parameters correctly.

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: it returns every article as one plain-text document for bulk ingestion. It explicitly contrasts with reading, search, and list tools, distinguishing itself from siblings like get_page, list_pages, and search_wiki.

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 provides explicit guidance: preflight with sizeOnly=true, pull with maxChars, narrow with tagPath, resume with skip=nextSkip, and use search/list first for questions. It also names an alternative URL access method, leaving no ambiguity about when and how to use the tool.

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

All Radix Wiki 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?