Skip to main content
Glama
yanmxa

Prometheus MCP Server

by yanmxa

prom_discover

Discover all available Prometheus metrics to identify what data can be queried for system monitoring and performance analysis.

Instructions

Discover all available metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:39-43 (registration)
    Registration of the 'prom_discover' tool in the exported tools array, including name, description, and empty input schema.
    {
      name: 'prom_discover',
      description: 'Discover all available metrics',
      inputSchema: { type: 'object', properties: {} },
    },
  • Dispatch handler in handleToolCall that invokes prometheusClient.discover() for the 'prom_discover' tool.
    case 'prom_discover': {
      result = await prometheusClient.discover();
      break;
    }
  • Core tool implementation: queries Prometheus API to discover available metric names (labels __name__).
    async discover(): Promise<PrometheusResponse<string[]>> {
      const response = await this.client.get<PrometheusResponse<string[]>>('/api/v1/label/__name__/values');
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Discover all available metrics' implies a read-only operation but doesn't specify whether this returns a complete list, paginated results, cached data, or real-time discovery. It lacks details about performance characteristics, rate limits, or authentication requirements that would help an agent understand how to properly invoke it.

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 perfectly concise at four words. It's front-loaded with the core action ('Discover') and resource ('available metrics'), with zero wasted words. Every element earns its place in this minimal but complete statement of function.

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 tool with no annotations, no output schema, and multiple sibling tools, the description is insufficiently complete. It doesn't explain what 'available metrics' means in context, how results are structured, or how this differs from prom_metadata which might provide similar information. The agent lacks enough context to understand when and how to use this tool effectively.

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 zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't waste space discussing non-existent parameters, though it could theoretically mention if there are implicit filters or scoping considerations not captured in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Discover all available metrics' states a clear purpose (discovering metrics) but lacks specificity about what resource or system this applies to. It doesn't differentiate from sibling tools like prom_metadata or prom_query, leaving ambiguity about what distinguishes this discovery operation from those alternatives.

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 its siblings. With tools like prom_metadata, prom_query, prom_range, and prom_targets available, there's no indication whether this is for initial exploration, comprehensive listing, or a specific type of metric discovery. The user must infer usage context 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.

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/yanmxa/prometheus-mcp-server'

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