Skip to main content
Glama

List backup vaults

list_backup_vaults
Read-only

List the organisation's backup vaults - the S3-compatible buckets cluster backups and migration data move through - with provider, bucket, verification status and last-verified time. Bucket credentials are never returned. 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_backup_vaults"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 largely redundant, but the description adds two things annotations cannot: the availability gate (backups must be enabled) and the security guarantee that bucket credentials are never returned. That is genuine behavioral context beyond the structured fields.

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 front-loaded sentence covering resource definition, returned fields, credential policy and availability. The em-dash appositive is dense but readable; minor redundancy with the annotation in 'Read-only' costs little but isn't earning its place.

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 correctly carries the return-value burden by naming the four fields and the credential exclusion, and it discloses the feature-gating condition. For a no-parameter read-only list, the only unaddressed item is whether results are paginated or scoped further, a small gap.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing a description could add about inputs. The description usefully spends that space describing the shape of what comes back instead.

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 the organisation's backup vaults'), then defines the resource concretely as S3-compatible buckets used for cluster backups and migration data. It also enumerates the fields returned (provider, bucket, verification status, last-verified time), which lets an agent distinguish it from the singular get_backup_vault sibling.

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?

Gives a real usage precondition: 'Only offered when backups are enabled for the organisation', which tells the agent when this tool will even exist. It does not explicitly route to get_backup_vault for per-vault detail, so the alternative-selection guidance is clear but not complete.

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.