Skip to main content
Glama

Get the Rithmo protocol

get_rithmo_protocol
Read-onlyIdempotent

Returns the Rithmo protocol: the steps you follow with Rithmo every run (start, a check before every action, approvals, end of run), its version and its content_hash. start_agent_run returns the same protocol in its answer. Takes no arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_rithmo_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint: false, and openWorldHint: false. The description adds useful behavioral detail by listing the protocol contents and confirming it takes no arguments, though it does not cover response structure or any freshness guarantees.

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?

The description is front-loaded with the return value, then summarizes the protocol contents, the sibling relationship, and the no-argument behavior. It is appropriately sized with no filler.

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?

For a simple no-argument read tool with rich annotations and no output schema, the description sufficiently explains what is returned and how it relates to start_agent_run. Nothing critical is missing for correct invocation.

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?

This is a zero-parameter tool, so the schema baseline is 4. The description reinforces this with 'Takes no arguments,' and no additional parameter semantics are needed.

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 and resource: 'Returns the Rithmo protocol,' then enumerates its contents including steps, version, and content_hash. It explicitly distinguishes this from the sibling start_agent_run, which returns the same protocol in its answer.

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?

Provides clear context that the protocol contains the steps followed every run and names start_agent_run as an alternative source of the same protocol. However, it does not explicitly state when to prefer this tool over starting a run or whether it should be fetched separately before taking actions.

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