Skip to main content
Glama

List backup vault imports

list_backup_vault_imports
Read-only

List the data imports a backup vault holds - the database dumps ankra migrate staged through the vault - with their cluster, stack, upload status, databases, warnings and restore progress. 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": {
      "vault_id": "<vault_id>"
    },
    "name": "list_backup_vault_imports"
  }
}

Input Schema

NameRequiredDescriptionDefault
vault_idYesBackup vault id (UUID) from list_backup_vaults.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and 'Read-only' merely repeats it. The real added value is beyond annotations: the description enumerates what each returned import carries (cluster, stack, upload status, databases, warnings, restore progress), which matters because there is no output schema. It says nothing about pagination or result volume.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the resource and its scope front-loaded, followed by the returned fields and a trailing safety note. No filler and nothing redundant.

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 one-parameter, read-only, no-output-schema list tool, the description covers purpose, the shape of the results, and the safety profile, which is enough to invoke it correctly. The remaining gap is operational detail: whether results are paginated or limited, and how warnings/progress are represented.

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?

Only one parameter and schema description coverage is 100%, with the schema already stating it is a UUID obtained from list_backup_vaults. The description adds no further meaning about the parameter beyond that baseline, so 3 is the correct floor.

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?

States a specific verb (list) and a precisely scoped resource (data imports held by one backup vault), and even defines what an import is (database dumps staged by `ankra migrate`). That tells an agent it is not list_backup_vaults, get_backup_vault, or list_restore_points. It stops short of naming those siblings explicitly, so it is clear but not fully differentiated.

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?

Usage is only implied: the vault_id parameter plus 'List the data imports a backup vault holds' makes the context inferable, and 'Read-only' signals this is safe inspection. There is no explicit when-to-use statement, no exclusion, and no pointer to the sibling that would be the alternative (e.g. get_backup_vault for vault-level detail).

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.