Skip to main content
Glama
pab1it0

Prometheus MCP Server

by pab1it0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Metric Metadata

get_metric_metadata
Read-onlyIdempotent

Retrieve metadata (type, help, unit) for Prometheus metrics. Use optional filter to search metric names and descriptions, or get all metadata without specifying a metric.

Instructions

Get metadata (type, help, unit) for metrics. Returns all metric metadata when no metric name is provided. Use filter_pattern to search metric names and descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricNo
filter_patternNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv1.2.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / filter_pattern
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / metric / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / metric / default
      Added value: +null
    • removedInput schema / properties / metric / title
      Removed value: -"Metric"
    • removedInput schema / properties / metric / type
      Removed value: -"string"
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "type": "integer"
+}
    • removedInput schema / required
      Removed value: -[
-  "metric"
-]
    • addedOutput schema / properties / result / anyOf
      Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]
    • removedOutput schema / properties / result / items
      Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / properties / result / type
      Removed value: -"array"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  2. Changed2 schema fields changedv1.0.0
    • removedInput schema / title
      Removed value: -"get_metric_metadataArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "_WrappedResult",
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds that it returns all metadata when no metric is given and how to use filter_pattern. No contradictions.

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?

Two efficient sentences with no redundancy. The first defines purpose, the second provides usage guidance. Every sentence adds value.

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?

With output schema present, description covers primary functionality. However, it omits explanation of pagination parameters (limit, offset), which could be important for large result sets. Otherwise complete.

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 0%, so description must compensate. It explains metric (optional, returns all if null) and filter_pattern (search). But it does not cover limit/offset, leaving pagination behavior unclear. Adequate but not fully compensating.

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

Purpose5/5

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

The description clearly states the tool retrieves metadata (type, help, unit) for metrics. It specifies behavior when no metric name is provided (returns all) and mentions filter_pattern for searching. This distinguishes it from siblings like list_metrics and execute_query.

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

Usage Guidelines4/5

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

Provides explicit guidance on using filter_pattern to search. However, it does not mention when not to use the tool or alternatives, but the context is clear enough for an agent to decide.

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

Deploy Server

Other Tools