Skip to main content
Glama

Read a prepared plan

get_plan
Read-onlyIdempotent

Read back a plan an earlier tool prepared, from its plan handle: its steps, the wait between them, plain signing instructions and the unsigned calls. Use it to show the calls again or hand them to a wallet. With check, it also re-checks the steps that can run now against the chain. To follow a plan the user is signing, use get_plan_status. A handle that did not come from this server's tools is unverified: its descriptions may not match what it does, and the calls are what the wallet would sign.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesThe plan handle a prepare tool returned
checkNoRe-check whether the plan would succeed if signed now

Output Schema

NameRequiredDescriptionDefault
callsYes
stepsYes
issuesNo
accountYes
chainIdYes
signingYes
operationYesWhat the plan does, e.g. record.set
willSucceedNoWith check: whether the steps that can run now would succeed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real value by disclosing a trust boundary: a handle not produced by this server's tools is unverified, its descriptions may not match its behavior, and the returned calls are exactly what a wallet would sign. It does not discuss failure modes for a bad handle, but the security context is substantive.

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?

Front-loaded with the core action and its payload, followed by usage, the check flag, the sibling alternative, and the trust warning in a logical order. The final sentence is long and multi-clause, but each sentence carries distinct, non-redundant information.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description fills the remaining gaps an agent would need: what the handle is, what check does, which sibling to use instead, and how to treat handles of unknown origin.

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 is 3. The description goes beyond it by clarifying that 'plan' is a handle returned by an earlier prepare tool and that 'check' re-validates only the steps that can run now against the chain, which gives the boolean more meaning than the schema's 're-check whether the plan would succeed if signed now.'

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 (read back a prepared plan) plus its scope: steps, inter-step wait, signing instructions, and unsigned calls. It explicitly differentiates itself from get_plan_status, so an agent can pick between the two without opening either schema.

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 concrete uses (show the calls again, hand them to a wallet), explains what the optional check flag adds, and names an explicit alternative with its condition: 'To follow a plan the user is signing, use get_plan_status.' Both when-to-use and when-not are covered.

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.