Skip to main content
Glama

metrics_query

Run an instant PromQL query to retrieve current metric values from a configured observability backend, with optional evaluation time and target selection.

Instructions

Execute an instant PromQL query and return current metric values.

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": {
      "query": "<query>"
    },
    "name": "metrics_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoEvaluation timestamp (ISO 8601 or Unix epoch). Defaults to now.
queryYesPromQL expression (e.g. rate(http_requests_total[5m]))
targetNoNamed backend instance to query (configured: default). Defaults to the primary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does establish that this is a read-only evaluation returning current values. It says nothing about authentication, backend availability, timeout or error behavior for malformed PromQL, or whether results are truncated.

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 front-loaded sentence with no filler, and the action plus return value come first. It is efficient, though the brevity leaves obvious gaps that a slightly longer sentence could have closed.

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 simple three-parameter read tool with full schema coverage and no output schema, the description covers the essentials. It omits the shape of results (instant vector samples, empty-result behavior) and the multi-backend implication of 'target', which an agent calling it would benefit from knowing.

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%, so the query, time, and target parameters are already fully documented in the schema; baseline is 3. The description's only added meaning is that evaluation defaults to now, which the schema already states for 'time'.

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 a specific verb (Execute) and resource (an instant PromQL query) and states the return (current metric values). The word 'instant' distinguishes it in spirit from a range-query sibling, but no sibling is named explicitly, so differentiation is only implicit.

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 implied by 'instant' vs a temporal-range alternative, and 'current metric values' suggests point-in-time inspection. However, there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. metrics_query_range), leaving the choice to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.