Skip to main content
Glama

Download database archive

databaseArchiveDownload
Read-onlyIdempotent

Get short-lived download links to the stored archive of one app’s archived managed database (state archived, or an unfinished restore of it) — Download the copy on the dashboard’s Database page. Only the owning account gets them, and they work for about ten minutes for whoever holds them: the links are bearer capabilities for the owning human’s private archive. artifact (the SQL a restore loads), manifest and, when the archive carries the app’s Storage files, files (one tar of them) each come with a size and SHA-256 to check the download. available: false carries a fixed code and a human-readable explanation instead of links; no_archive means the database is not archived, so there is no copy to download: while the database is ready, its data is the database itself. It changes nothing and returns no database 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>"
    },
    "name": "databaseArchiveDownload"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
codeYes
filesNo
messageYes
artifactYes
manifestYes
availableYes
projectIdYes
archivedAtYes
retainUntilYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: links are short-lived (~ten minutes), bearer capabilities, restricted to the owning account, and each artifact ships with size and SHA-256 for verification. It also documents the failure shape (`available: false` with a fixed `code`), explains `no_archive`, and explicitly states nothing is mutated and no database credential is returned — consistent with readOnlyHint and destructiveHint=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 and the ten-minute bearer-link warning are front-loaded and earn their place. However, the enumeration of `artifact`/`manifest`/`files` with sizes and checksums largely restates what the output schema already provides, and the closing clause about the database being its own data is wordier than needed.

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?

For a one-parameter read tool with an output schema and full annotations, the description covers everything an agent needs: eligibility state, link lifetime, authorization scope, verification data, and error codes. No material gap remains.

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% and the description never names `projectId` or explains it directly. The single parameter is a self-evident project UUID whose meaning is implied by "one app's archived managed database," so the gap is minor but not filled.

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: "Get short-lived download links to the stored archive of one app's archived managed database." It also scopes the eligible states (`archived` or an unfinished restore) and distinguishes itself from backup/restore siblings by making clear it returns links, not data or credentials.

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 a clear precondition for use (database must be archived) and points to the dashboard Database page as an equivalent path. It does not explicitly name a sibling tool as the alternative for the non-archived case (e.g. a backup or status tool), so the routing guidance is strong but not 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.

Resources