Radix Wiki

Send feedback

send_feedback

Tell the maintainers of the Radix Wiki what you needed and did not find, what is wrong, or what broke. One issue per call, in 300 characters at most. Reports are read, not published.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "message": "<message>"
    },
    "name": "send_feedback"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	missing: not covered here. wrong: a fact or link is out of date or false. broken: a tool or page failed. suggestion: anything else.
`page`	No	The page path, URL or tool it is about, if any
`message`	Yes	What you were after, or what is wrong and what it should say. 300 characters at most.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write-but-safe profile is already covered. The description adds real context the annotations cannot: reports are private to maintainers ('read, not published') and must be scoped to a single issue within 300 characters, which shapes how the agent composes the call.

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 short sentences, zero filler, with the audience and allowed content front-loaded before the submission constraints. Nothing repeats the schema verbatim.

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 3-parameter submission tool with no output schema, this covers purpose, triggers, and limits. The only gap is what the caller gets back after submitting (acknowledgment, ticket id), which an agent might want when confirming the report landed.

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%, including a documented enum for 'kind', so the baseline is 3. The description still contributes a constraint not in the schema — one issue per call — which tells the agent how to split multi-problem feedback across invocations.

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 concrete verb and audience ('Tell the maintainers of the Radix Wiki') plus the exact content expected ('what you needed and did not find, what is wrong, or what broke'). This is unmistakably distinct from the page CRUD and read siblings, so an agent can route to it 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?

The enumerated triggers (missing content, incorrect content, breakage) define when to reach for this tool, and 'One issue per call' sets the granularity expectation. It stops short of naming an alternative channel or saying when not to use it, so it falls just below the explicit when/when-not bar.

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?