Skip to main content
Glama

metrics_query_range

Execute PromQL range queries against a configured observability backend to return time-series data for a specified time window and resolution.

Instructions

Execute a range PromQL query and return a time series.

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>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "metrics_query_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesRange end (ISO 8601 or Unix epoch)
stepNoQuery resolution step (e.g. "15s", "1m", "5m")60s
queryYesPromQL expression
startYesRange start (ISO 8601 or Unix epoch)
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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and delivers almost none of it. It does not disclose result-size limits, how the step parameter affects resolution or cost, whether queries time out, or what errors look like for a backend query tool.

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, verb and resource first and the return shape last. It is efficient, though the brevity borders on under-specification rather than tight economy.

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

Completeness2/5

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

For a five-parameter query tool with no annotations and no output schema, one sentence is thin. The agent gets no information on result limits, step/resolution tradeoffs, target failover behavior, or error conditions — all things the schema and annotations do not cover.

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 all five parameters (query, start, end, step, target) are already documented in the schema. The description adds no meaning beyond that — for example, it never explains how step interacts with start/end or what target selection implies. Baseline 3 applies.

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 states a specific verb and resource ('Execute a range PromQL query') plus the return shape ('return a time series'), so an agent knows this is a range/evaluation-window query. It does not explicitly differentiate itself from the sibling metrics_query, leaving the instant-vs-range distinction to be inferred from the word 'range'.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites, and no mention of the obvious alternative (metrics_query for instant queries). The agent must infer selection criteria from the tool name alone.

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