Skip to main content
Glama

metrics_label_values

Retrieve all values for a specified Prometheus label, such as jobs, instances, or status codes, to inspect available metric dimensions.

Instructions

Get all values for a given Prometheus label (e.g. list all jobs, instances, or status codes).

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": {
      "label": "<label>"
    },
    "name": "metrics_label_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYesLabel name (e.g. "job", "instance", "status_code")
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.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Get' implies a read, but it says nothing about whether the call is cheap or expensive at high cardinality, how results are ordered or truncated, or what the response looks like (plain list vs structured values). Only the schema's 'target' note about backend selection partially fills this gap.

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 padding, and the examples earn their place by clarifying the kind of label intended. Slightly marred by the parenthetical mixing free-form descriptions ('status codes') with actual label names used elsewhere ('status_code').

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?

This is a simple two-parameter read tool with no output schema, so the description should at least characterize the return shape (a list of label values) and any truncation behavior. It gestures at returning 'all values' but leaves result format and limits unstated, which is the main remaining gap.

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 both the 'label' and 'target' parameters are already documented. The description reinforces the label parameter with example values but adds no new semantics such as accepted label-name casing or backend-selection behavior beyond 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?

States a specific verb and resource ('Get all values for a given Prometheus label') and parenthesizes concrete examples (jobs, instances, status codes) that make the resource type unambiguous. It is clearly distinct from metrics_query or metrics_metadata by virtue of being a label-value enumerator, though it never names a sibling to contrast with.

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 label-discovery framing suggests calling this before building a metrics_query filter, but there is no explicit 'use this when…' or 'not for…' statement. It also does not say whether this is the metrics counterpart to logs_label_values or how the two are chosen between.

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