Radix Wiki

Whole corpus

get_full_corpus

Read-onlyIdempotent

The whole of the Radix Wiki as one text document, for bulk ingestion. Preflight first: sizeOnly=true returns the character count, a token estimate, the per-branch breakdown and the largest pages. Then pull it with maxChars (default 200000, max 1000000), or one branch at a time with tagPath. Truncation is page-aligned: truncated, omittedPages and nextSkip say where to resume (pass skip=nextSkip). For a handful of pages get_pages is cheaper.

Input Schema

Name	Required	Description
`skip`	No	Resume from this page index: the `nextSkip` of the previous truncated call (default 0)
`tagPath`	No	One branch and its descendants. Omit for everything.
`maxChars`	No	Character budget for `document` (default 200000, max 1000000)
`sizeOnly`	No	Sizes and breakdowns only, no document. Do this before the first real pull.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 20, 2026
- addedInput schema / properties / maxChars / maximum
```
Added value: +1000000
```
- addedInput schema / properties / maxChars / minimum
```
Added value: +1000
```
- addedInput schema / properties / skip / minimum
```
Added value: +0
```

Changed3 schema fields changedOct 19, 2026

changedInput schema / properties / sizeOnly / description

Previous value: -"Return sizes and breakdowns only, no document. Do this before the first real pull."New value: +"Sizes and breakdowns only, no document. Do this before the first real pull."

changedInput schema / properties / skip / description

Previous value: -"Resume from this page index — pass the `nextSkip` from the previous truncated call (default 0)"New value: +"Resume from this page index: the `nextSkip` of the previous truncated call (default 0)"

changedInput schema / properties / tagPath / description

Previous value: -"Restrict to one branch and its descendants, e.g. \"contents/tech\". Omit for everything."New value: +"One branch and its descendants. Omit for everything."

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

A4.9/5.0

Behavior5/5

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

Annotations cover only safety (readOnly/idempotent/closed-world), and the description adds the behavior that actually matters for a large dump: page-aligned truncation, truncated/omittedPages/nextSkip resume protocol, skip=nextSkip continuation, and the default/max character budget. That is substantial disclosure beyond structured fields.

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?

One dense paragraph that is front-loaded with the resource, then the preflight, then paging/resume, then the alternative. Every clause carries operational information; nothing is 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?

With no output schema, the description carries the return-value burden itself, naming truncated, omittedPages, nextSkip and the sizeOnly report fields. For a 4-param, zero-required bulk-read tool, an agent has everything needed for a correct first call and a correct continuation.

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

Parameters4/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 still adds meaning the schema does not carry, notably what sizeOnly=true actually returns (character count, token estimate, per-branch breakdown, largest pages) and the preflight-then-pull sequencing. It does not add format/syntax detail for skip or tagPath beyond the schema, so it stops short of a 5.

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?

Specific verb+resource: returns the whole Radix Wiki as one text document for bulk ingestion, which is unambiguous against a sibling list dominated by single-page/browsing tools. It also explicitly contrasts itself with get_pages for small fetches, so an agent can route 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?

Gives an explicit workflow: preflight with sizeOnly=true, then pull with maxChars, or narrow to one branch with tagPath, and use get_pages instead for a handful of pages. When-to-use, when-not, and the alternative are all stated.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?