Skip to main content
Glama

prom_targets

Monitor Prometheus scrape target health status to identify infrastructure monitoring issues and ensure reliable metrics collection.

Instructions

Show Prometheus scrape target health status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The scrapeTargets function fetches target health information from the Prometheus API and formats it into a table.
    export async function scrapeTargets(): Promise<string> {
      const url = `${config.prometheusUrl}/api/v1/targets`;
      const res = await fetch(url);
      if (!res.ok) throw new Error(`Failed to fetch targets: ${res.status}`);
    
      interface Target { labels: Record<string, string>; scrapeUrl: string; health: string; lastScrape: string; lastError: string; }
      const data = (await res.json()) as { data: { activeTargets: Target[] } };
      const activeTargets = data.data?.activeTargets || [];
    
      if (activeTargets.length === 0) return "No active scrape targets found.";
    
      const headers = ["JOB", "ENDPOINT", "STATE", "LAST SCRAPE", "ERROR"];
      const rows = activeTargets.map((t: {
        labels: Record<string, string>;
        scrapeUrl: string;
        health: string;
        lastScrape: string;
        lastError: string;
      }) => [
        t.labels.job || "unknown",
        t.scrapeUrl,
        t.health,
        t.lastScrape ? new Date(t.lastScrape).toLocaleTimeString() : "N/A",
        (t.lastError || "").substring(0, 40),
      ]);
    
      const healthy = activeTargets.filter((t: { health: string }) => t.health === "up").length;
      const total = activeTargets.length;
    
      return `Scrape targets (${healthy}/${total} healthy):\n\n${formatTable(headers, rows)}`;
    }
  • The definition of the 'prom_targets' tool in the registerPrometheusTools function.
      name: "prom_targets",
      description: "Show Prometheus scrape target health status",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • The mapping of 'prom_targets' to the scrapeTargets handler in handlePrometheusTool.
    case "prom_targets": return scrapeTargets();
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 burden of behavioral disclosure. It states 'show' which implies a read-only operation, but doesn't specify whether it requires authentication, rate limits, or what the output format looks like. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured.

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?

Given the tool has no parameters and no output schema, the description adequately covers the basic purpose. However, without annotations or output details, it lacks information on behavioral traits like authentication needs or return format, making it minimally complete but with clear gaps for practical use.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it appropriately doesn't mention any, earning a baseline score for tools with no parameters.

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 clearly states the verb 'show' and the resource 'Prometheus scrape target health status', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like prom_active_alerts or prom_alert_rules, which also show Prometheus-related information but focus on different aspects.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on the name alone without explicit direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/batu-sonmez/infraclaude'

If you have feedback or need assistance with the MCP directory API, please join our Discord server