Skip to main content
Glama

Upgrade a database to a larger size

resize_database
Idempotent

Moves the database to a LARGER size (more vCPU, memory and included disk; see get_database_options): same data, users, names and addresses. It restarts: one to two minutes of downtime, status maintenance meanwhile (resize.to_gb set), then active with the new size_gb. The new rate applies from the next hour. Larger sizes only, there is no way back: tell the user the new price and the downtime first. 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>",
      "size_gb": "<size_gb>"
    },
    "name": "resize_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
size_gbYesMemory in GB, larger than the current size_gb.
databaseYesDatabase id, as returned by list_databases or create_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.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, so 'retrying the same call is safe' mostly restates structured data. The description does add genuinely new behavior: a restart with one to two minutes of downtime, a maintenance status with resize.to_gb set, and the new rate applying from the next hour. The irreversibility note ('there is no way back') is scoped to size and does not conflict with destructiveHint=false, since data, users and addresses are preserved.

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?

Front-loads the scope and irreversibility, then the operational details, with no filler. It is dense to the point of being packed, but every clause carries decision-relevant information.

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?

No output schema exists, and the description covers what happens after the call (maintenance status, then active with the new size_gb) plus the cost and downtime implications an agent must surface. Nothing needed to call it correctly is missing.

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 coverage is 100%, so size_gb, database and idempotency_key are already documented, and the 'larger than the current size_gb' constraint is repeated from the schema. The only added meaning is pointing at get_database_options as the source of valid sizes, which is marginal beyond the structured fields.

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 ('Moves the database to a LARGER size') and immediately scopes it with the exact resource dimensions affected (vCPU, memory, included disk) while distinguishing it from update_database by being size-only. An agent can tell this apart from siblings 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 Guidelines5/5

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

Gives explicit preconditions and exclusions: larger sizes only, no way back, tell the user the new price and downtime first, and consult get_database_options for valid sizes. Both the when and the when-not are stated.

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.