Skip to main content
Glama

Verify backup vault

verify_backup_vault
Destructive

Re-run the platform's credential check against a backup vault's bucket and report the new status (the twin of ankra backup vaults verify). Use this after rotating or fixing the vault's access keys. Requires backups.operate.

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

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
Behavior3/5

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

The description adds genuinely useful context beyond the annotations: it states the required permission (backups.operate) and that the call returns the new status, which the annotations do not convey. However, the annotations declare destructiveHint=true and idempotentHint=false, and the description never explains what is destructive about re-running a check or why repeated calls are not idempotent. That gap is notable for a flagged-destructive operation.

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?

Three short sentences: what it does, when to use it, what it requires. The action is front-loaded and no sentence is filler.

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 tool with no output schema, the description covers purpose, trigger, and permission, which is close to sufficient. The main omission is any explanation of the destructive behavior flagged in annotations, which an agent should know before invoking.

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?

There is a single parameter with 100% schema description coverage ('Backup vault id (UUID) from list_backup_vaults'), so the schema already carries the semantics and the description adds nothing further about vault_id. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource: 'Re-run the platform's credential check against a backup vault's bucket and report the new status.' This clearly distinguishes it from a plain read like get_backup_vault, since it re-executes a check rather than fetching stored state. It also anchors the tool to a known CLI command ('the twin of `ankra backup vaults verify`'), though it does not explicitly name a sibling tool as the alternative.

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?

'Use this after rotating or fixing the vault's access keys' gives a concrete trigger condition for invocation. It provides clear context but no exclusions or explicit statement of when another tool (e.g., get_backup_vault for a passive read) would be preferred.

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.