Radix Wiki

Read a page

get_page

Read-onlyIdempotent

Read one page in full: its extracted text, current version number, update date and declared metadata. Takes either the single path a listing returns or the tagPath/slug pair it splits into — not a URL and not a title. A wrong pair is answered with the tools that find a right one rather than an empty result. For the whole article set at once use get_full_corpus, and for a page as markdown fetch its URL with .md appended.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	No	The whole path in one string, e.g. "contents/tech/core-concepts/utxo-model" — the form every listing returns as `url`. Use this or the tagPath/slug pair.
`slug`	No	Page slug (e.g. "utxo-model")
`tagPath`	No	Tag path (e.g. "contents/tech/core-concepts")

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 6, 2026

addedInput schema / properties / path

Added value: +{
+  "description": "The whole path in one string, e.g. \"contents/tech/core-concepts/utxo-model\" — the form every listing returns as `url`. Use this or the tagPath/slug pair.",
+  "type": "string"
+}

addedInput schema / requireOneOf
```
Added value: +[
+  "path",
+  "slug"
+]
```

removedInput schema / required

Removed value: -[
-  "tagPath",
-  "slug"
-]

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 already mark the operation as read-only and idempotent; the description adds meaningful behavioral context on top, such as the fact that a wrong pair returns tools that find the right page rather than an empty result, and that the tool returns the full content plus metadata. This helps set agent expectations beyond the structured 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?

Three sentences carry dense, relevant information with no filler. The first sentence states the core purpose and return contents, the second clarifies input constraints, and the third points to alternatives. It is front-loaded and every sentence earns its place.

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?

The description is complete for a read-only, single-page retrieval tool. It covers what is returned, how to identify the page, what kind of input is invalid, how errors behave, and which sibling tools or URL forms to use for different goals. No output schema exists, but the return contents are enumerated sufficiently.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining the relationship between parameters: you can pass either the single path or the tagPath/slug pair, and explicitly warns against non-supported forms like URLs or titles. This goes beyond the individual property descriptions.

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 action ('Read one page') and names the exact resource and the data returned: extracted text, version number, update date, and declared metadata. It also distinguishes itself from get_full_corpus and the markdown-via-URL path, so an agent can identify which tool fits.

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 explicitly says when to use this tool ('for the whole article set at once use get_full_corpus') and when to use a different mechanism ('for a page as markdown fetch its URL with .md appended'). It also clarifies what forms of input are acceptable and what is not accepted: 'not a URL and not a title'.

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?