Skip to main content
Glama

Follow a plan

get_plan_status
Read-onlyIdempotent

Follow a prepared plan after the user signs it, e.g. 'I sent the commit, what now?'. Give the plan handle and the hashes of the transactions sent so far, each with its step (none before signing). Returns each step's state (confirmed, pending, reverted, waiting, ready or blocked), the registration commitment's window, whether the next step would succeed now and what to do next. Once every step is confirmed it names the tool that shows the result.

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": {
      "plan": "<plan>"
    },
    "name": "get_plan_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesThe plan handle a prepare tool returned
transactionsNoTransactions the user sent, each with the step it signs

Output Schema

NameRequiredDescriptionDefault
doneYes
nextYesWhat the user should do next
stepsYes
issuesYesWhy the next step would fail if signed now, or why a step reverted
accountYes
warningsYes
operationYes
commitmentNoRegistration only: when the register step may be sent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description adds genuine behavioral context by enumerating possible step states (confirmed, pending, reverted, waiting, ready or blocked), mentioning the registration commitment's window, and noting the next-step feasibility check. It also discloses the terminal behavior: once all steps are confirmed it names the tool that shows the result. No contradiction with annotations.

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?

Three sentences, front-loaded with the trigger and example before the input requirements and return summary. Dense but every clause carries information; the parenthetical '(none before signing)' earns its place, though the enumerated state list makes the middle sentence slightly heavy.

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 two-parameter read tool with an output schema and full annotation coverage, the description covers trigger, inputs, and the shape of the response, including what to do next. The only gap is that it never explicitly routes the agent away from get_plan, which matters given the near-identical sibling name.

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%, so the baseline would be 3, but the description adds real meaning beyond the schema: the transactions array holds hashes 'sent so far' and should be empty before signing ('none before signing'), and each entry must be paired with the step it signs. This resolves the ambiguity of when to pass an empty array versus omit it.

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 opens with a specific verb and resource: 'Follow a prepared plan after the user signs it,' plus a concrete example utterance. It distinguishes the tool's job (tracking step state after signing) from a prepare tool, but it never names or contrasts with the sibling get_plan, which an agent could easily confuse with this one.

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?

It states the trigger condition ('after the user signs it'), gives a realistic caller phrasing ('I sent the commit, what now?'), and tells the agent exactly what to supply ('the plan handle and the hashes of the transactions sent so far, each with its step'). No explicit when-not guidance or named alternative is provided, which keeps it short of a 5.

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.