Skip to main content
Glama

Switch Rithmo on or off for this agent

set_agent_governance
Read-only

Only when the person who owns this agent asks, in their own words, to turn Rithmo on or off for it: on true or false, said their words, run the run they started. Refused off when their company requires Rithmo for this agent.

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": {
      "agent_key": "<agent_key>",
      "on": "<on>"
    },
    "name": "set_agent_governance"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes
runNo
saidNo
agent_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior1/5

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

The description plainly describes a state-changing operation ('turn Rithmo on or off'), while annotations declare readOnlyHint=true. That is a direct inconsistency about whether the call mutates anything. The only genuine behavioral addition is the policy refusal ('Refused off when their company requires Rithmo'), which does not offset the contradiction.

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

Conciseness3/5

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

Compact and front-loaded on the precondition, but the telegraphic phrasing ('`run` the run they started') is ambiguous rather than efficient, and the refusal clause is tacked on without indicating what happens on refusal.

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

Completeness3/5

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

With no output schema and 0% schema coverage across four params, the description should explain the return/refusal outcome and the required `agent_key`. It hints at refusal but not at what the caller sees, leaving an agent guessing about the result of a governance change.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load. It loosely glosses `on`, `said` and `run`, but leaves the required `agent_key` unexplained and gives no formats, lengths, or examples beyond tautologies like 'their words'.

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?

The description states a specific verb and resource: turning 'Rithmo' on or off for a given agent, keyed by `agent_key` plus the `on` boolean. It is not a tautology of the title, though it offers no differentiation from siblings such as update_agent or get_rithmo_protocol, and 'Rithmo' is never defined.

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?

Explicit gating: only invoke when the agent's owner asks in their own words, and the request must carry their words (`said`) and the `run` they started. This is clear when-to-use guidance, though no alternative tool is named for cases where the precondition fails.

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