Scribase

backup.restore

Destructive

Restore a verified backup into a target environment. POST .../backups/{backup_id}/restore. Source environment is named by environment_id; target by target_environment_id.

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": {
      "organization_id": "<organization_id>",
      "project_id": "<project_id>",
      "environment_id": "<environment_id>",
      "backup_id": "<backup_id>",
      "target_environment_id": "<target_environment_id>",
      "confirm": "<confirm>"
    },
    "name": "backup.restore"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Must be true to apply this mutation; otherwise the tool returns the request it would send for approval.
`backup_id`	Yes	backup_id (required)
`project_id`	Yes	project_id (required)
`environment_id`	Yes	environment_id (required)
`organization_id`	Yes	organization_id (required)
`target_environment_id`	Yes	target_environment_id (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. However, for a destructive restore the description says nothing about what happens to existing data in the target environment, whether the operation is asynchronous, or whether it is reversible — the most important behavioral facts an agent needs before invoking it.

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?

Two short sentences, front-loaded with the action and followed by the endpoint and the source/target mapping. No filler, though the raw endpoint path is of marginal value to an agent.

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?

With six required parameters, no output schema, and a destructive mutation, the description covers the identity of the operation but omits outcome semantics (what the target becomes, whether prior state is lost, how completion is reported). Adequate to select the tool, thin for invoking it safely.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by clarifying that environment_id names the source and target_environment_id names the destination — a distinction the schema's bare 'environment_id (required)' labels do not convey.

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 gives a specific verb and resource ('Restore a verified backup into a target environment') and even names the endpoint path, so the operation is unambiguous. It does not explicitly distinguish itself from the similarly named sibling branches.restore, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus backup.create, backup.get, or branches.restore, and no stated prerequisites beyond the word 'verified'. The agent must infer the usage context entirely from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Scribase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?