Skip to main content
Glama
dimonb

Uptrace MCP Server

by dimonb

uptrace_list_monitors

List all alerting monitors to view IDs, names, types, and configurations for monitoring setup management.

Instructions

List all alerting monitors. Returns monitor IDs, names, types, and configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the uptrace_list_monitors tool. It calls client.get_monitors() and formats the output as text.
    elif name == "uptrace_list_monitors":
        logger.info("Listing monitors")
        monitors = client.get_monitors()
    
        lines = [
            "# Monitors",
            f"**Total Monitors**: {len(monitors)}",
            "",
        ]
    
        if monitors:
            lines.append("## Monitor List")
            for monitor in monitors:
                lines.append(f"- **{monitor.name}** ({monitor.type}) [ID: {monitor.id}]")
        else:
            lines.append("No monitors found.")
    
        return [TextContent(type="text", text="\n".join(lines))]
  • The Tool definition and registration for uptrace_list_monitors in the MCP server.
    Tool(
        name="uptrace_list_monitors",
        description="List all alerting monitors. Returns monitor IDs, names, types, and configuration.",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
Behavior3/5

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

With no annotations provided, the description carries the full burden. It partially compensates by disclosing return values (IDs, names, types, configuration), but omits other behavioral traits like pagination, rate limits, permissions required, or performance characteristics of listing 'all' items.

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 consists of two efficient sentences with zero waste: the first states the action, the second states the return value. It is appropriately front-loaded and sized for a simple parameterless tool.

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 zero-parameter list tool with no output schema, the description is reasonably complete. It compensates for the missing output schema by describing what fields are returned (IDs, names, types, configuration), though it could mention pagination or result limits.

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 input schema has 0 parameters, establishing a baseline score of 4. The description correctly implies no filtering is possible by stating 'List all,' which aligns with the empty schema.

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 (List), resource (alerting monitors), and scope (all). It implicitly distinguishes from sibling 'uptrace_get_monitor' (list vs. get) and 'uptrace_list_dashboards' (monitors vs. dashboards), though it doesn't explicitly name 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 siblings like 'uptrace_get_monitor' (which likely retrieves a single monitor) or when listing all monitors is inappropriate. No prerequisites or exclusions are mentioned.

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/dimonb/uptrace-mcp'

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