Skip to main content
Glama

Bring back archived database

databaseRestore

Restore one owned app’s archived database (Bring it back on its Database page) into a NEW managed database, check it and reconnect the app, never writing over a database or deleting anything. Requires confirmName, the app’s exact name, representing the human’s agreement to restore this exact app; a wrong name is refused. It needs the account’s plan to include a managed database: if not, payment_required sends the human to the Tofu dashboard, where the account’s plan is managed. The answer is a report, not an error: its message is human-readable. in_progress is not a failure: Tofu carries it on by itself. unverified and files_failed copies are never connected to the app. requiresDeployment true: deploy the app again so its build sees the new connection settings. Sign-in accounts come back; everyone signs in again. reentry names sign-in secrets to supply again: this tool neither takes nor returns the values. It returns no credential.

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": {
      "projectId": "<projectId>",
      "confirmName": "<confirmName>"
    },
    "name": "databaseRestore"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
confirmNameYes

Output Schema

NameRequiredDescriptionDefault
atYes
refYes
codeYes
stateYes
sha256Yes
actorIdYes
archiveYes
enabledYes
messageYes
outcomeYes
reentryNo
rewriteNo
projectIdYes
artifactKeyYes
verificationYes
requiresDeploymentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true; the description goes well beyond that by explaining that the restore lands in a brand-new managed database, that nothing is overwritten or deleted, that `in_progress` is not a failure, that `unverified`/`files_failed` copies are never reconnected, and that the app must be redeployed. It also discloses the credential boundary: `reentry` names secrets to re-supply but the tool neither takes nor returns them. This is consistent with destructiveHint=false and idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, which is good, but the body is a dense chain of colon-separated fragments with heavy backticked jargon (`reentry`, `unverified`, `files_failed`) and an odd UI aside in parentheses. Most sentences carry real information, yet the run-on phrasing and undeclared terms make it harder to scan than it needs to be.

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?

An output schema exists, yet the description still usefully pre-frames the response as a report with a human-readable `message` and a non-failing `in_progress` state, plus the redeploy follow-up and credential re-entry. The main gap is the undefined `projectId` and no word on downtime or expected duration during the restore, which matters for a state-changing operation.

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 description coverage is 0%, so the description carries the burden. It explains `confirmName` thoroughly — the exact app name, a proxy for human agreement, with wrong names refused — but never defines `projectId` beyond the loose phrase 'one owned app', leaving the agent to infer it is the app/project identifier. Half the parameters are well served, half are not.

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 opens with a precise verb and resource: restore one owned app's archived database into a NEW managed database, and explicitly states it never overwrites or deletes anything. That is far more specific than the title alone. It stops short of differentiating itself from the sibling databaseRestoreRequest, which an agent must still disambiguate on its own.

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?

It gives clear preconditions (the account plan must include a managed database, otherwise `payment_required` routes the human to the dashboard) and a hard gate (`confirmName` must match the exact app name). It also implies a follow-up step (`requiresDeployment` true means redeploy). What it lacks is any explicit statement of when NOT to use it versus the sibling restore-request tool.

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