Skip to main content
Glama

Fork a database

fork_database
Idempotent

Creates a NEW database, billed like any other, whose data is an instant copy of this one (for a test or staging copy), with the same users and passwords. It stays linked to its source for up to 7 days (no backups of its own, the source cannot be deleted) unless detach_database_fork ends that sooner. Retrying the same call is safe. Scope: vms.create.

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": {
      "database": "<database>",
      "name": "<name>"
    },
    "name": "fork_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpcNoDefault: the source's private network; same region either way.
nameYesName of the new database.
size_gbNoMemory in GB, one of the sizes of get_database_options for the region. Default: 1, or the source's size.
databaseYesThe source database.
idempotency_keyNoYour own unique value per order. By default one is derived from the call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Your own unique value per order. By default one is derived from the call."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description carries substantial behavior the annotations do not: the fork is billed as a normal database, it has no backups of its own, the source cannot be deleted while the link exists, the link expires after 7 days, and the call is safe to retry. It also discloses the required permission scope (vms.create), which is unusual and highly useful pre-call context.

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?

A single dense sentence, but it is front-loaded with the core action and copy semantics before moving to lifecycle and billing constraints; every clause conveys a distinct fact. Slightly heavy clause nesting (the "unless detach_database_fork..." aside) costs a point on parseability.

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 mutation tool with no output schema, the description covers cost implications, lifecycle and expiry, source-side side effects, idempotency, and required scope — everything an agent needs to decide and call safely. Retrieval of the resulting database is covered by existing sibling tools, so no return-value explanation is needed.

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 100%, including defaults for vpc, size_gb, and idempotency_key, so the schema already does the parameter work. The description adds only indirect context ("same users and passwords") and no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

"Creates a NEW database ... whose data is an instant copy of this one" gives a specific verb, resource, and the defining property that separates it from a plain create_database (which would produce an empty instance). The parenthetical "for a test or staging copy" anchors the intent further, so an agent can select it 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?

It states the intended use case (test or staging copy) and names detach_database_fork as the tool that ends the fork relationship early, which is real routing guidance. It stops short of explicitly contrasting with create_database or restore_database, so the agent must infer that a blank new instance or a backup restore is the alternative path.

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.