Skip to main content
Glama

Radix Wiki

by wiki.radix
OverviewDiscussionsAdmin

Create a page

create_page

Create a new Radix Wiki page. Requires a ROLA bearer token; see https://radix.wiki/AGENTS.md for the challenge-sign-verify flow. Call get_categories first for a valid tagPath. Needs a wallet holding at least 10,000 $XRD (ecosystem 20,000, blog 50,000, ideas 10,000), a balance check that spends nothing. Earns contribution points.

Input Schema

NameRequiredDescriptionDefault
slugNoURL slug (derived from the title when omitted)
titleYesPage title
contentYesArray of typed blocks. Start with an infobox, hyperlink every assertion to its source, no inline styles.
tagPathYesTag path the page lives under (e.g. "contents/tech/core-concepts")
metadataNoKey-value metadata for the page, including `excerpt` (one sentence, ≤160 chars). Some tag paths require specific keys — the error names any that are missing.
bannerImageNoBanner image URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / content / items / properties / metric / enum
      Previous value: -[
-  "transactions",
-  "activeAccounts",
-  "newAccounts",
-  "newComponents",
-  "newResources",
-  "nftsMinted",
-  "feesXrd",
-  "burnedXrd",
-  "royaltiesXrd"
-]New value: +[
+  "transactions",
+  "activeAccounts",
+  "newAccounts",
+  "newComponents",
+  "newResources",
+  "nftsMinted",
+  "feesXrd",
+  "royaltiesXrd"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / content / items / description
      Previous value: -"A typed block with a unique `id` (UUID) and a `type`. A `content` block carries semantic HTML in `text`; an `infobox` carries nested `blocks`. For any other type, copy the shape of one already on a page: get_page with `blocks: true` (or GET /api/wiki/{path}) returns blocks as stored."New value: +"A typed block with a unique `id` (UUID) and a `type`. A `content` block carries semantic HTML in `text`; an `infobox` carries nested `blocks`. An `events` block carries `items: [{ id, date, end?, text }]`, each date a year, month or day (`2026`, `2026-11`, `2026-11-12`) and `text` inline HTML saying what and where, in any order: the page sorts them into upcoming and past by the day it is read. A `locations` block carries `items: [{ id, name?, address?, map?, phone?, email?, hours?, timeZone?, note? }]`, each with its address (plain text, a line to a line) or its `hours`, rows of `{ days: [\"mon\"…\"sun\"], opens: \"08:00\", closes: \"18:00\" }`; the page groups the days and says whether each place is open by its own clock. For any other type, copy the shape of one already on a page: get_page with `blocks: true` (or GET /api/wiki/{path}) returns blocks as stored."
    • changedInput schema / properties / content / items / properties / type / enum
      Previous value: -[
-  "content",
-  "banner",
-  "columns",
-  "list",
-  "assetPrice",
-  "networkChart",
-  "rssFeed",
-  "codeTabs",
-  "linkGrid",
-  "tipJar",
-  "references",
-  "infobox",
-  "stats",
-  "testimonial"
-]New value: +[
+  "content",
+  "banner",
+  "columns",
+  "list",
+  "assetPrice",
+  "networkChart",
+  "rssFeed",
+  "codeTabs",
+  "linkGrid",
+  "tipJar",
+  "references",
+  "locations",
+  "events",
+  "infobox",
+  "stats",
+  "testimonial"
+]
  3. Changed7 schema fields changed
    • addedInput schema / properties / content / items / properties / count
      Added value: +{
+  "description": "How many of the newest (list)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / content / items / properties / pageIds
      Removed value: -{
-  "description": "Page ids in display order (pageList): the `id` get_page returns with `blocks: true`",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / content / items / properties / pages
      Added value: +{
+  "description": "Page ids in display order (list, `chosen`): the `id` get_page returns with `blocks: true`",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}
    • addedInput schema / properties / content / items / properties / show
      Added value: +{
+  "description": "Each page as a link with its age, or as a card with its banner and opening line (list)",
+  "enum": [
+    "links",
+    "cards"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / content / items / properties / source
      Added value: +{
+  "description": "Where a list's pages come from (list): `under` the pages in the category `under` names, `newest` the newest `count` pages (within `under` if given), `chosen` the pages in `pages`",
+  "enum": [
+    "under",
+    "newest",
+    "chosen"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / content / items / properties / type / enum
      Previous value: -[
-  "content",
-  "banner",
-  "columns",
-  "recentPages",
-  "pageList",
-  "assetPrice",
-  "networkChart",
-  "rssFeed",
-  "codeTabs",
-  "linkGrid",
-  "tipJar",
-  "references",
-  "infobox",
-  "stats",
-  "testimonial"
-]New value: +[
+  "content",
+  "banner",
+  "columns",
+  "list",
+  "assetPrice",
+  "networkChart",
+  "rssFeed",
+  "codeTabs",
+  "linkGrid",
+  "tipJar",
+  "references",
+  "infobox",
+  "stats",
+  "testimonial"
+]
    • addedInput schema / properties / content / items / properties / under
      Added value: +{
+  "description": "A tag path, such as `contents/tech` (list)",
+  "type": "string"
+}
  4. Changed5 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"Array of typed blocks. Each needs a unique `id` (UUID) and a `type`. A `content` block carries semantic HTML in `text`; an `infobox` block carries nested `blocks`. Start with an infobox, hyperlink every assertion to its source, no inline styles."New value: +"Array of typed blocks. Start with an infobox, hyperlink every assertion to its source, no inline styles."
    • addedInput schema / properties / content / items / additionalProperties
      Added value: +true
    • addedInput schema / properties / content / items / description
      Added value: +"A typed block with a unique `id` (UUID) and a `type`. A `content` block carries semantic HTML in `text`; an `infobox` carries nested `blocks`. For any other type, copy the shape of one already on a page: get_page with `blocks: true` (or GET /api/wiki/{path}) returns blocks as stored."
    • addedInput schema / properties / content / items / properties
      Added value: +{
+  "blocks": {
+    "description": "Nested leaf blocks (infobox)",
+    "items": {
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "id": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "metric": {
+    "description": "The series charted (networkChart)",
+    "enum": [
+      "transactions",
+      "activeAccounts",
+      "newAccounts",
+      "newComponents",
+      "newResources",
+      "nftsMinted",
+      "feesXrd",
+      "burnedXrd",
+      "royaltiesXrd"
+    ],
+    "type": "string"
+  },
+  "pageIds": {
+    "description": "Page ids in display order (pageList): the `id` get_page returns with `blocks: true`",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "text": {
+    "description": "Semantic HTML (content, banner)",
+    "type": "string"
+  },
+  "type": {
+    "enum": [
+      "content",
+      "banner",
+      "columns",
+      "recentPages",
+      "pageList",
+      "assetPrice",
+      "networkChart",
+      "rssFeed",
+      "codeTabs",
+      "linkGrid",
+      "tipJar",
+      "references",
+      "infobox",
+      "stats",
+      "testimonial"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / content / items / required
      Added value: +[
+  "id",
+  "type"
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the generic non-read-only, non-destructive, non-idempotent profile; the description adds real context the annotations cannot: authentication mechanism, wallet-holding requirements per tag category, the fact the balance check spends nothing, and the contribution-points side effect. It omits failure behavior for duplicate slugs/titles, which matters for a non-idempotent create.

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?

Four dense sentences, front-loaded with the action and followed by prerequisites in rough order of execution. Parenthetical category thresholds are a little crammed, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with a deep nested content schema and no output schema, the description covers auth, sequencing, eligibility and content style. It does not say what the call returns (page id/path) or how conflicts are surfaced, which an agent needs to chain into get_page or edit_page.

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% and the nested block schema is heavily self-documented, so the baseline is 3. The description still adds value beyond the schema by imposing content conventions (start with an infobox, hyperlink every assertion, no inline styles) and by pointing tagPath at get_categories for valid values.

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?

Opens with a specific verb+resource ("Create a new Radix Wiki page") that is unmistakably distinct from the siblings edit_page, delete_page and get_page. It also names the immediate prerequisite tool (get_categories), so an agent can place it in the workflow without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete preconditions: a ROLA bearer token with a linked challenge-sign-verify flow, a call to get_categories first for a valid tagPath, and a per-category wallet balance threshold. It never explicitly says when NOT to use it (e.g. use edit_page to modify an existing page), so it falls short of full when/when-not/alternatives coverage.

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