Skip to main content
Glama

Call a Rithmo step

rithmo_action
Read-only

Calls the Rithmo tool named by action with args, exactly as calling that tool by name would. Use it for any Rithmo step your Rithmo protocol names that your host does not list as a tool. The answer is that tool's answer.

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": {
      "action": "<action>"
    },
    "name": "rithmo_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Adds real behavioral context beyond the annotations: the call is transparent forwarding, and the return value is the target tool's answer. However, the annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=false) describe the dispatcher, not the arbitrary target it invokes, and the description never warns that the effective safety profile is the target's. Error handling for an unknown or invalid `action` is also unstated.

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, front-loaded with the mechanism and followed by the selection rule and return-value note. No filler, no restatement of the title, and every sentence adds distinct information.

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?

With no output schema, the description correctly closes the return-value question ('the answer is that tool's answer') and explains how the action name is sourced. Remaining gaps for a free-form dispatcher are failure modes — unknown action, invalid args, and the fact that the safety annotations do not transfer to the target tool.

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 0%, so the description carries the full burden and mostly succeeds: `action` is the name of a Rithmo tool (drawn from the protocol's named steps) and `args` are that tool's arguments, established by the phrase 'exactly as calling that tool by name would.' It stops short of saying where the authoritative list of valid `action` names comes from or what form the name takes (case, prefix), which matters at 0% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and mechanism: it calls the Rithmo tool named by `action`, passing `args`, and returns that tool's answer. That tells an agent exactly what this is (a dispatcher/indirection tool) without opening either schema, though the distinction from the other listed Rithmo tools is conveyed by role rather than by naming any of them.

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 selection rule: use it for Rithmo steps your protocol names that your host does not list as a tool. The implicit alternative — invoking that tool directly by name — is named and declared equivalent, so the agent knows when this tool is redundant and when it is required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources