Skip to main content
Glama

List restore points

list_restore_points
Read-only

List restore points newest first (the twin of ankra cluster stacks restore-points list and ankra backup restore-points list). Name a cluster and stack for one stack's history, or neither for the organisation-wide listing - a restore point outlives the cluster it came from. Every row carries not_carried: what the capture did NOT take, and why. Read-only. Only offered when backups are enabled for the organisation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_restore_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, 1 to 100. Defaults to 20; narrow with the filters rather than raising it.
statusesNoRestrict to these statuses, e.g. complete, creating, error.
triggersNoRestrict to these trigger kinds, e.g. scheduled, manual.
cluster_idNoUUID of the cluster. Alternative to cluster_name.
stack_nameNoRestrict to one stack. Needs its cluster named too.
cluster_nameNoExact name of the cluster. Optional when a cluster is already selected in the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so 'Read-only' is mildly redundant, but the description adds genuinely new behavior: results are newest-first, restore points outlive their source cluster (so org-wide listings include orphaned entries), every row carries a not_carried field explaining capture gaps, and availability is gated on backups being enabled for the organisation. Pagination or result-count behavior is not covered.

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?

Five short sentences, front-loaded with the core action and ordering, then scoping rules, then the notable output field and gating. The CLI-twin parenthetical is useful for agents mapping from command-line workflows but is the one element an agent could do without.

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?

Six optional parameters with no output schema, and the description covers selection modes, ordering, the one non-obvious return field (not_carried), and the feature-gate precondition. What is missing is result-volume behavior (pagination, totals) for a tool whose limit defaults to 20.

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, but the description adds real meaning beyond it: the cluster+stack pairing rule and the neither-parameter organisation-wide fallback are stated as a coherent rule rather than two isolated field notes. It does not add examples or defaults for statuses/triggers/limit, which the schema already documents.

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 ('List restore points'), the ordering ('newest first'), and the scoping modes (one stack's history vs organisation-wide). An agent can distinguish this from get_restore_point or delete_restore_point 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?

Explicitly tells the agent how to choose between the two modes: name cluster and stack for one stack's history, or neither for the organisation-wide listing. It also flags the gating condition ('only offered when backups are enabled'). It does not name a specific alternative sibling for looking up a single restore point, which would have made it 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.