Skip to main content
Glama

Get restore point

get_restore_point
Read-only

Show one restore point in full: its status, size, verification, the assets it carries, the run that produced it, and not_carried - what it does NOT contain and why. Discover ids with list_restore_points. Read-only. Only offered when backups are enabled for the organisation.

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": {
      "stack_name": "<stack_name>",
      "restore_point_id": "<restore_point_id>"
    },
    "name": "get_restore_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the cluster. Alternative to cluster_name.
stack_nameYesThe stack the restore point belongs to. Two clusters can hold a stack of the same name, so the stack and cluster are what address it.
cluster_nameNoExact name of the cluster. Optional when a cluster is already selected in the conversation.
restore_point_idYesRestore point id (UUID) from list_restore_points.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description reinforces that ("Read-only") and adds a genuine environmental constraint — the tool exists only when backups are enabled for the organisation — which the agent cannot learn from annotations. It also discloses that the response includes not_carried, a non-obvious coverage field, without saying anything about permissions or sizing.

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?

The core action is front-loaded, followed by the returned fields and then the discovery and availability notes. The field enumeration is long but each item is substantive; there is minor redundancy in restating "Read-only" alongside the annotation.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does so concretely, including the unusual not_carried section. It covers addressing and availability well; the only gap is silence on authorization or size/volume limits for large restore points.

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 100%, so stack_name, cluster_name, cluster_id and restore_point_id are already documented in the schema, including the note that restore_point_id comes from list_restore_points. The description repeats the discovery pointer but adds no new meaning about how a restore point is addressed across clusters; baseline 3 applies.

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?

"Show one restore point in full" gives a specific verb and single-resource scope, then enumerates what the payload contains (status, size, verification, assets, producing run, not_carried). That reads clearly as the detail counterpart to list_restore_points, so an agent can pick it over the sibling without opening a schema.

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 names list_restore_points as the way to obtain ids and states an availability precondition (only offered when backups are enabled for the organisation), which is actionable routing context. It stops short of explicit when-not guidance versus adjacent siblings such as get_backup_posture or the restore/delete restore-point tools.

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.