Skip to main content
Glama

Back up or restore dynamic data

manage_dynamic_backup
DestructiveIdempotent

Creates, lists or restores supported application backups. Restoring replaces current data and requires the exact project-name confirmation. Backup availability depends on the project plan.

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": {
      "project_id": "<project_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "manage_dynamic_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_keyNo
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
confirmationNo
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's job is to add scope, which it does: restore overwrites current data, a confirmation value is mandatory, and plan tier gates availability. It does not explain list-mode behavior or what a successful restore/create returns, keeping it below 5.

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?

Three short sentences with the capability stated first and the risky behavior front-loaded in the middle. No filler, though the mode-selection mechanics are omitted rather than merely condensed.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-mode, destructive, four-parameter tool with no output schema, the definition covers preconditions well but leaves a critical hole: it never explains which parameters trigger list versus create versus restore, or how backup_key and confirmation interact with each mode.

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 50%: project_id and idempotency_key are documented in the schema, while backup_key and confirmation are not. The description adds real meaning for confirmation (must be the exact project name) but says nothing about backup_key, so it only partially compensates for the gap.

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 the resource (application backups) and the three verbs (create, list, restore) in a single sentence, which is clearly distinguishable from project/deployment siblings. It falls short of 5 because the three verbs are bundled into one tool without saying how the caller selects a mode.

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?

'Restoring replaces current data and requires the exact project-name confirmation' gives a prerequisite for the restore path, and 'availability depends on the project plan' sets a precondition. However, no guidance distinguishes when to list versus create versus restore, and no alternative tool or fallback is named.

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.

Resources