Skip to main content
Glama

Database statistics

get_database_metrics
Read-only

CPU, memory, connections and commits per minute (commands per minute on Valkey) over 1h (1-minute buckets), 24h (10 minutes) or 7d (1 hour); only buckets with samples. Scope: vms.read.

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

Input Schema

NameRequiredDescriptionDefault
rangeNoPeriod covered. Default 24h.
databaseYesDatabase id, as returned by list_databases or create_database.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / range / description
      Added value: +"Period covered. Default 24h."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real additional weight: it discloses the per-range bucket resolution, that only buckets containing samples are returned (sparse series, no zero-fill), and the vms.read scope requirement. It stops short of describing units or ordering, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One densely packed sentence with zero filler, and the metric list is front-loaded before the range/granularity detail and the scope note. The nested parentheticals and semicolons make it slightly hard to parse on first read, but nothing is redundant.

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

Completeness4/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 does the work of naming the returned series and their resolution, plus the sparse-bucket caveat and the required scope, which is enough for an agent to call it correctly. Minor omissions such as units and timestamp format are tolerable for a read-only metrics endpoint.

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 genuinely adds meaning: it maps each enum value to its bucket size (1-minute, 10-minute, 1-hour), which the schema's 'Period covered' text does not. The database id parameter gets no added semantics beyond the schema's pointer to list_databases.

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 names the exact signals returned (CPU, memory, connections, commits per minute, with the Valkey-specific 'commands per minute' variant), so an agent knows precisely what data this yields. It reads as a resource-plus-contents description rather than an explicit verb, and it never states it is database-scoped versus the VM or load-balancer metric siblings, so differentiation relies partly on the tool name.

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: the granularity table (1h/24h/7d with bucket sizes) hints at which range to pick for which horizon, and 'Scope: vms.read' tells the agent a permission is required. There is no explicit when-to-use or when-not guidance, and no routing to alternatives such as get_slow_queries or get_database for other database information.

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.