Skip to main content
Glama

Provision backup vault

provision_backup_vault
Destructive

Create a backup vault and let Ankra create its bucket at the provider from a stored provider credential (the twin of ankra backup vaults provision). No bucket keys travel here: the credential does the creation and the resulting keys go straight to the vault. Requires backups.manage and the organisation's backups feature. get_backup_vault reports the verification once the lane finishes.

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": {
      "name": "<name>",
      "credential_id": "<credential_id>"
    },
    "name": "provision_backup_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe vault's name in Ankra.
bucketNoBucket name to create; omit to let Ankra choose.
regionNoProvider region for the bucket, when the provider needs one.
credential_idYesUUID of the provider credential (from list_credentials) that creates the bucket.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, non-idempotent, destructive operation, and the description adds real context on top: no bucket keys transit the call, the stored credential performs the provider-side creation, and generated keys land directly in the vault. It also discloses the permission and feature-flag prerequisites plus the asynchronous verification lane, though it says nothing about what a failed or partial provisioning leaves behind.

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?

The primary action is front-loaded in the first clause, and the parenthetical CLI twin locates it quickly for users who know the CLI. A few phrases, such as the CLI-equivalence note, are useful orientation rather than filler, though the text is denser than strictly necessary.

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 destructive mutation with no output schema, the description covers purpose, prerequisites, secret-handling behaviour, and the follow-up read tool, which is most of what an agent needs. Remaining gaps are failure semantics and confirmation requirements, which matter given destructiveHint=true.

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%, so each parameter's meaning is already documented, including that omitting bucket lets Ankra choose. The description reinforces the role of credential_id (a stored provider credential doing the creation) but adds no format, constraint, or interaction details beyond the schema.

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 (create a backup vault) plus the secondary action (Ankra creates the bucket at the provider from a stored credential). It also names the read counterpart get_backup_vault, so an agent can separate provisioning from reporting 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?

Gives clear context for use: requires backups.manage and the organisation's backups feature, and it points to get_backup_vault for the later verification step. It does not explicitly exclude near neighbours such as create_object_storage_bucket or verify_backup_vault, so the routing is implied rather than exhaustive.

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.