Skip to main content
Glama
dimonb

Uptrace MCP Server

by dimonb

uptrace_list_dashboards

Retrieve all dashboard IDs and names from the Uptrace observability platform for monitoring and analysis.

Instructions

List all dashboards. Returns dashboard IDs and names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'uptrace_list_dashboards' tool, which fetches dashboards from the client and formats them as markdown text.
    elif name == "uptrace_list_dashboards":
        logger.info("Listing dashboards")
        dashboards = client.get_dashboards()
    
        lines = [
            "# Dashboards",
            f"**Total Dashboards**: {len(dashboards)}",
            "",
        ]
    
        if dashboards:
            lines.append("## Dashboard List")
            for dashboard in dashboards:
                lines.append(f"- **{dashboard.name}** [ID: {dashboard.id}]")
                if dashboard.description:
                    lines.append(f"  {dashboard.description}")
        else:
            lines.append("No dashboards found.")
  • The Tool registration for 'uptrace_list_dashboards'.
    Tool(
        name="uptrace_list_dashboards",
        description="List all dashboards. Returns dashboard IDs and names.",
        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 of behavioral disclosure. It successfully discloses the return format (IDs and names) but fails to mention critical operational traits like pagination behavior, rate limits, permission requirements, or whether 'all' implies unbounded retrieval versus a default limit.

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 short sentences with zero redundancy. The first states the action and resource; the second states the return value. Every word earns its place and critical information is front-loaded.

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 low complexity (zero parameters, simple list operation) and absence of an output schema, the description adequately compensates by specifying the return payload structure. It loses a point only for omitting pagination or result limiting behavior, which is important for 'list all' operations that could return large datasets.

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 contains zero parameters. Per evaluation guidelines, 0 params warrants a baseline score of 4. The description appropriately does not invent parameters, though it could have mentioned that no filtering is possible (confirming the schema intent).

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 uses specific verb 'List' with clear resource 'dashboards' and explicit scope 'all'. The second sentence clarifies the specific return payload ('dashboard IDs and names'), providing precise expectations about what data is retrieved without needing to read an output schema.

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 like the search_* siblings (e.g., uptrace_search_services) or get_* tools. It does not mention prerequisites, filtering limitations, or why one might prefer listing all dashboards versus querying specific metrics directly.

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