Skip to main content
Glama

Restore status

fleet__restore_status
Read-onlyIdempotent

Where a restore of one site stands: running (with its stage and percent), completed or failed (with SiteVault's message). Takes the site_id and the restore_id shown on the applied restore. Read only.

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": {
      "site_id": "<site_id>",
      "restore_id": "<restore_id>"
    },
    "name": "fleet__restore_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes
restore_idYesThe restore id the applied restore shows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so 'Read only' is largely a restatement. The genuinely additive content is the response-state enumeration (running with stage and percent, completed/failed with SiteVault's message), which matters because no output schema exists. That is useful but it does not say whether failed states include remediation hints or whether polling is rate-limited.

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?

One compact sentence chain with the state information front-loaded and no filler. 'Read only.' is a redundant trailing sentence given readOnlyHint=true, so it is not maximally economical, but nothing else wastes space.

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 no output schema, the description carries the essential information: what is returned in each state and where restore_id comes from. Missing only terminal-state behavior (e.g., how long a completed/failed result remains retrievable), which is a modest gap rather than a blocker.

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 50%: restore_id is documented in the schema, site_id is a bare string. The description fills the gap by tying restore_id to the id 'shown on the applied restore', telling the agent where to obtain the value, and identifies site_id as the site being restored. Site_id's expected format is still unstated, keeping this short of a 5.

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 concrete verb-substitute and resource: it reports where a restore of one site stands, and enumerates the observable states (running with stage and percent, completed, failed). That is enough to separate it from fleet__restore_from_snapshot in intent, though it never names the sibling explicitly, so the reader must infer the start-vs-poll pairing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Takes the site_id and the restore_id shown on the applied restore' implies the tool is used after a restore has been applied, which is real if indirect usage context. However, it never says when not to use it, whether it should be polled repeatedly, or whether it stops being valid once the restore is completed or failed — all left to inference.

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