Skip to main content
Glama
pab1it0

Prometheus MCP Server

Get Scrape Targets

get_targets
Read-onlyIdempotent

Retrieve scrape target information from Prometheus monitoring to identify active endpoints and their status for metric collection.

Instructions

Get information about all scrape targets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_targets' tool using FastMCP's @mcp.tool decorator. Defines the tool's description, title, icon, and operational hints.
        description="Get information about all scrape targets",
        annotations={
            "title": "Get Scrape Targets",
            "icon": "🎯",
            "readOnlyHint": True,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": True
        }
    )
  • The handler function for the 'get_targets' tool. Makes a request to Prometheus API '/api/v1/targets' and returns a dictionary containing 'activeTargets' and 'droppedTargets' lists.
    async def get_targets() -> Dict[str, List[Dict[str, Any]]]:
        """Get information about all Prometheus scrape targets.
    
        Returns:
            Dictionary with active and dropped targets information
        """
        logger.info("Retrieving scrape targets information")
        data = make_prometheus_request("targets")
        
        result = {
            "activeTargets": data["activeTargets"],
            "droppedTargets": data["droppedTargets"]
        }
        
        logger.info("Scrape targets retrieved", 
                    active_targets=len(data["activeTargets"]), 
                    dropped_targets=len(data["droppedTargets"]))
        
        return result
Behavior4/5

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

Annotations already provide strong behavioral hints (readOnlyHint: true, destructiveHint: false, etc.), so the bar is lower. The description adds value by specifying 'all scrape targets', implying no filtering capabilities, which is useful context beyond annotations. No contradictions with annotations are present.

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 with no wasted words. It's appropriately sized for a simple tool with no parameters and good annotations, making it easy to parse and understand quickly.

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?

Given the tool's simplicity (0 parameters, annotations covering safety and behavior, and an output schema), the description is reasonably complete. It specifies the resource ('scrape targets') and scope ('all'), though it could be more detailed about the type of information returned, but the output schema mitigates this gap.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the input structure. The description appropriately doesn't add parameter details, as none are needed, earning a baseline score of 4 for this context.

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 'Get information about all scrape targets' clearly states the verb ('Get') and resource ('scrape targets'), but it's vague about what specific information is retrieved. It doesn't distinguish this tool from sibling tools like 'get_metric_metadata' or 'list_metrics', which also appear to retrieve information about different resources.

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. There's no mention of context, prerequisites, or comparisons to sibling tools like 'get_metric_metadata' or 'list_metrics', leaving the agent without explicit usage instructions.

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

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