Skip to main content
Glama

Update a database

update_database
Idempotent

Any of: the name; the weekly maintenance window (day 0 = Sunday, start hour, Montréal time, 2 hours long; minor updates, usually under 2 minutes of downtime); the disk cap (the disk grows by itself at 80 % full, up to the cap; disk beyond what the size includes is billed per GB); on Valkey, the eviction policy. Scope: databases.write.

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": "update_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name; the connection host does not change.
databaseYesDatabase id, as returned by list_databases or create_database.
disk_cap_gbNoLargest size in GB the disk may grow to by itself; disk beyond what the size includes is billed per GB.
eviction_policyNoValkey only: what happens when data memory is full. noeviction (default) refuses writes; allkeys-lru removes the least used keys, for a cache.
maintenance_dayNoDay of the weekly maintenance window: 0 is Sunday, 6 is Saturday.
maintenance_hourNoHour the 2-hour window starts, 0 to 23, Montréal time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / disk_cap_gb / description
      Added value: +"Largest size in GB the disk may grow to by itself; disk beyond what the size includes is billed per GB."
    • addedInput schema / properties / maintenance_day / description
      Added value: +"Day of the weekly maintenance window: 0 is Sunday, 6 is Saturday."
    • addedInput schema / properties / maintenance_hour / description
      Added value: +"Hour the 2-hour window starts, 0 to 23, Montréal time."
    • addedInput schema / properties / name / description
      Added value: +"New display name; the connection host does not change."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (idempotent, non-destructive, open-world), the description discloses real operational behavior: the maintenance window is a fixed 2-hour slot that usually causes under 2 minutes of downtime, a disk grows automatically at 80% full up to the cap, and overflow is billed per GB. The required write scope is also stated. It does not say whether omitted fields are left untouched or when changes take effect, which keeps it short of a 5.

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 semicolon-separated field list is dense and reasonably short, but it is front-loaded with a fragment rather than a purpose statement, and the per-GB billing sentence is repeated nearly verbatim from the schema, costing space without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation tool with no output schema, the description covers side effects, billing, and permissions well, and annotations carry idempotency and safety. What is missing is the partial-update contract (whether unspecified settings stay unchanged) and the shape of the result, both of which an agent needs to invoke it confidently.

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 already 100%, so the baseline is 3, and the description genuinely adds meaning: maintenance hours are Montréal time, the window is 2 hours long with minor downtime, the disk cap interacts with automatic growth at 80% and per-GB billing beyond the included size, and eviction_policy applies to Valkey only. Only the name and eviction clauses largely restate the schema.

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 enumerates exactly which database settings can be modified (name, maintenance window, disk cap, Valkey eviction policy), which is specific about the resource and scope. It never opens with a plain statement of the verb, starting instead with the fragment 'Any of:', and it does not distinguish itself from siblings like resize_database, whose territory the disk_cap_gb field arguably overlaps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by the field list and the trailing 'Scope: databases.write', which tells the agent the permission required but not when to pick this tool over resize_database or update_firewall. There are no explicit when-to-use or when-not-to-use conditions and no named alternative.

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.