Skip to main content
Glama

Get backup vault

get_backup_vault
Read-only

Show one backup vault: provider, endpoint, region, bucket, verification status, error excerpt and timestamps. Bucket credentials are never returned. Discover vault ids with list_backup_vaults. 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": "get_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

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 redundant but consistent. The description adds real behavioral context beyond the annotations: the exact field set returned and the important guarantee that bucket credentials are never returned, which prevents an agent from expecting or asking for secrets.

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, front-loaded with the resource and its returned fields, followed by the security caveat and the id-discovery pointer. No filler or restated title text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 return-value burden and does so by listing the returned fields and the credential exclusion. Combined with the id-discovery pointer and read-only framing, an agent has everything needed to call it correctly.

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% and the single vault_id parameter is already documented as a UUID sourced from list_backup_vaults. The description repeats that provenance but adds no format or validation detail beyond the schema, so the 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?

States a specific verb and resource ("Show one backup vault") and then enumerates exactly what is returned: provider, endpoint, region, bucket, verification status, error excerpt, timestamps. An agent can distinguish this from list_backup_vaults or get_backup_posture without opening the 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 routes the agent to the sibling list_backup_vaults for vault id discovery, which is the main usage question for a single-resource getter. It does not state when-not to use it (e.g. bulk listing or posture checks), but for a narrow read-only lookup that is a minor gap.

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.