Skip to main content
Glama

Radix Wiki

by wiki.radix
OverviewDiscussionsAdmin

Read a page

get_page
Read-onlyIdempotent

One page of the Radix Wiki in full: its text, version, update date and metadata. Address it by path ("tag/path/slug", exactly the path or url a listing returns), or by tagPath + slug; a category's own path reads its hub article. Not a title. For 2 to 20 pages call get_pages, one round trip rather than N. A miss names the nearest pages, so a wrong guess is fixed in one retry. A page's URL with .md appended is its markdown. With blocks: true, content is the stored block array, ids and all, beside the page id and its whole metadata: read a page this way before editing it, and send its version back as the edit's baseVersion.

Input Schema

NameRequiredDescriptionDefault
pathNoThe page's whole path, e.g. "developers/scrypto/blueprints". Preferred over tagPath + slug.
slugNoPage slug. Ignored when `path` is set.
blocksNoReturn the stored blocks rather than prose, for an edit
tagPathNoTag path only ("" for a top-level page). Ignored when `path` is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / blocks
      Added value: +{
+  "description": "Return the stored blocks rather than prose, for an edit",
+  "type": "boolean"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / path / description
      Previous value: -"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."New value: +"The page's whole path, e.g. \"developers/scrypto/blueprints\". Preferred over tagPath + slug."
    • changedInput schema / properties / slug / description
      Previous value: -"Page slug (e.g. \"utxo-model\"). Ignored when `path` is set."New value: +"Page slug. Ignored when `path` is set."
    • changedInput schema / properties / tagPath / description
      Previous value: -"Tag path (e.g. \"contents/tech/core-concepts\"). Ignored when `path` is set."New value: +"Tag path only (\"\" for a top-level page). Ignored when `path` is set."
  3. Changed2 schema fields changed
    • changedInput schema / properties / slug / description
      Previous value: -"Page slug (e.g. \"utxo-model\")"New value: +"Page slug (e.g. \"utxo-model\"). Ignored when `path` is set."
    • changedInput schema / properties / tagPath / description
      Previous value: -"Tag path (e.g. \"contents/tech/core-concepts\")"New value: +"Tag path (e.g. \"contents/tech/core-concepts\"). Ignored when `path` is set."
  4. Changed3 schema fields changed
    • 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"
-]
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld=false, but the description adds non-obvious behavior: a miss names the nearest pages (self-correcting in one retry), blocks:true returns the stored block array with ids alongside page id and full metadata, and the returned version is the baseVersion an edit expects. Those editorial/workflow details are not in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the core purpose leads, then addressing, then sibling routing, then edge behaviors. Nearly every clause carries information, though the middle section (miss behavior, .md markdown, blocks workflow) is tightly packed and could be split slightly for scanning.

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?

No output schema exists, so the description carries the burden of describing returns (text, version, update date, metadata; block array under blocks:true) and does so. For a read tool with a clear safety profile, nothing an agent needs to call it correctly or use the result (e.g., baseVersion) is missing.

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 baseline is 3, and the description goes beyond it: it establishes precedence ('path' preferred, tagPath/slug ignored when set), states the concrete path format ('tag/path/slug'), and explains what blocks:true actually yields and why (pre-edit read). This adds meaning the schema strings alone don't convey.

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?

States a specific verb+resource (read one page in full: text, version, update date, metadata) and distinguishes itself from siblings by naming get_pages and the collection-vs-single boundary. The addressing modes (path, or tagPath+slug) are spelled out, so an agent can tell it apart from list_pages/search_wiki without opening a 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?

Explicit routing rule: 'For 2 to 20 pages call get_pages, one round trip rather than N.' It also warns 'Not a title' and clarifies that a category's own path reads its hub article, plus the edit workflow (read with blocks:true before editing). When-to-use and when-to-use-the-alternative are both covered.

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

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