Skip to main content
Glama
dimonb

Uptrace MCP Server

by dimonb

uptrace_get_monitor

Retrieve detailed information about a specific monitoring configuration by providing its unique ID within the Uptrace observability platform.

Instructions

Get details of a specific monitor by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monitor_idYesID of the monitor to retrieve

Implementation Reference

  • The handler implementation for the uptrace_get_monitor tool, which retrieves monitor details and formats them as text.
    elif name == "uptrace_get_monitor":
        monitor_id = arguments.get("monitor_id")
        if not monitor_id:
            return [TextContent(type="text", text="Error: monitor_id is required")]
    
        logger.info(f"Fetching monitor: {monitor_id}")
        monitor = client.get_monitor(monitor_id)
    
        import json
    
        lines = [
            f"# Monitor: {monitor.name}",
            f"- **ID**: {monitor.id}",
            f"- **Type**: {monitor.type}",
            f"- **Notify Everyone**: {monitor.notify_everyone_by_email}",
            "",
            "## Parameters",
            f"```json\n{json.dumps(monitor.params, indent=2)}\n```",
        ]
    
        if monitor.team_ids:
            lines.append(f"- **Team IDs**: {monitor.team_ids}")
        if monitor.channel_ids:
            lines.append(f"- **Channel IDs**: {monitor.channel_ids}")
        if monitor.repeat_interval:
            lines.append(f"- **Repeat Interval**: {monitor.repeat_interval}")
    
        return [TextContent(type="text", text="\n".join(lines))]
  • The registration and input schema definition for the uptrace_get_monitor tool.
    Tool(
        name="uptrace_get_monitor",
        description="Get details of a specific monitor by ID.",
        inputSchema={
            "type": "object",
            "properties": {
                "monitor_id": {
                    "type": "string",
                    "description": "ID of the monitor to retrieve",
                },
            },
            "required": ["monitor_id"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'Get' but does not confirm this, nor does it describe error handling (e.g., behavior if ID not found), return format, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. However, given the lack of annotations and output schema, it may be overly terse—leaving no room for behavioral context that would help an agent understand failure modes or return values.

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?

For a simple single-parameter lookup tool, the description meets the minimum threshold by stating the core function. However, with no output schema and no annotations, the description should ideally describe what details are returned or error conditions to be considered 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 100%, with the parameter 'monitor_id' fully documented in the schema itself. The description adds no additional parameter semantics beyond what the schema provides, warranting a baseline score.

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 uses a clear verb ('Get') and resource ('monitor') with scope ('by ID'), making the basic function unambiguous. However, it does not explicitly differentiate from sibling tool 'uptrace_list_monitors' (e.g., stating to use this when the ID is known).

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?

No guidance provided on when to use this tool versus alternatives like 'uptrace_list_monitors' or what prerequisites are needed (e.g., having the monitor ID). The description states what the tool does but not when to invoke it.

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