Skip to main content
Glama

Create a database

create_database
Idempotent

Orders a managed database (PostgreSQL, MySQL, MariaDB or Valkey) in a private network, billed by the hour from now (the account needs 24 hours of credit), or by the month (730 hours) or the year (ten months) with billing; get_database_options gives each price. A monthly or yearly period comes out of credit if it covers it; otherwise billing.pending_invoice holds the invoice to pay and it stays hourly until then. Ready within minutes (status pending → active), with the admin user ffxfadmin and the logical database defaultdb (Valkey: the admin default, no logical database). 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": {
      "name": "<name>",
      "vpc": "<vpc>"
    },
    "name": "create_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpcYesPrivate network the database joins (list_vpcs); the machines on it reach the database.
nameYesDisplay name of the database, 1 to 64 characters.
engineNoDefault postgresql. mysql is Percona Server; valkey is Redis-compatible (key-value, in memory).
billingNohourly (default), monthly (the price of 730 hours, paid in advance) or yearly (ten months). Ask the user; monthly or yearly needs credit or an invoice paid by the user.
size_gbNoMemory in GB, one of the sizes of get_database_options for the region. Default: 1, or the source's size.
versionNoMajor version from get_database_options; the newest by default.
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 / name / description
      Added value: +"Display name of the database, 1 to 64 characters."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the billing model and its credit/invoice fallback, the provisioning timeline (pending → active within minutes), the resulting admin user ffxfadmin and defaultdb, the Valkey exception, and the required scope vms.create. The retry-safety statement is consistent with idempotentHint=true.

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?

The core action is front-loaded and every clause carries information, but it reads as a dense run-on chain of sentences that could be split for scanability. No filler or restated title text.

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?

With no output schema, the description supplies the return-relevant facts an agent needs: resulting status progression, admin credentials naming, logical database naming, and the pending_invoice field. For a 7-parameter provisioning tool this is unusually complete.

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: how billing interacts with credit and invoices, the Valkey no-logical-database case, and the defaults the order produces. It stops short of explaining version or size_gb selection beyond deferring to get_database_options.

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 ('Orders a managed database') and enumerates the engines (PostgreSQL, MySQL, MariaDB, Valkey) plus the private-network placement, so the agent can distinguish this provisioning call from get_database_options or create_database_user 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?

Gives clear preconditions for the billing choice (24 hours of credit required; monthly/yearly consumes credit or leaves a pending_invoice) and points to get_database_options for pricing. It does not say when to prefer this over sibling paths such as fork_database or restore_database, so it falls short of explicit when-not guidance.

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.