Skip to main content
Glama

metrics_targets

Lists all Prometheus scrape targets and their health status, optionally for a named backend instance, to help identify unhealthy targets.

Instructions

List all Prometheus scrape targets and their health status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "metrics_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. "List all" implies a read-only, non-destructive operation and names the payload (targets plus health status), but says nothing about permissions, pagination, or whether results are scoped to a single backend.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

One front-loaded sentence with no filler; the resource and the returned attribute come first and nothing is repeated or wasted.

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?

For a simple read-only list tool with one optional parameter and no output schema, the description covers purpose and returned content. It could say slightly more about what a target entry contains, but nothing critical to correct invocation is missing.

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 coverage is 100% and the sole optional 'target' parameter already documents the named backend instance and its default. The description adds only the 'all targets' implication, which is marginal value beyond the schema – the baseline 3 is appropriate.

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?

"List all Prometheus scrape targets and their health status" states a specific verb (list), a specific resource (scrape targets), and what is returned (health status). It is clearly distinct from siblings like metrics_query or metrics_metadata, though it does not name them to reinforce the distinction.

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?

The narrow 'scrape targets' scope implies when to use it versus the query/label siblings, but the description never states the condition explicitly or rules out alternatives. Guidance is inferred rather than given.

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