Skip to main content
Glama
mcp-server-devops
by Feliper83

Grafana Dashboard Summary

grafana_dashboard_summary

Fetch a Grafana dashboard's title and panel list by UID to inspect its structure. Returns mock dashboards when no Grafana backend is configured.

Instructions

Fetch a Grafana dashboard's title and panel list by UID. Connects to a real Grafana instance when MCP_GRAFANA_URL and MCP_GRAFANA_API_KEY are set; otherwise returns mock dashboards ("telecom-provisioning", "k8s-cluster-overview") so the tool is demoable without infra.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "<uid>"
    },
    "name": "grafana_dashboard_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesDashboard UID, e.g. telecom-provisioning

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description must carry behavioral disclosure, and it does well by explaining that it connects to a real Grafana instance when MCP_GRAFANA_URL and MCP_GRAFANA_API_KEY are set, otherwise returning specific mock dashboards. This is important operational context. It does not cover error behavior or explicitly state read-only semantics, keeping it below a 5.

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 two sentences, front-loaded with the core action and followed by the environment fallback behavior. Every phrase contributes useful information without repetition or filler. The mock dashboard names are compactly presented and aid understanding.

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 simple one-parameter read tool with no output schema, the description adequately states what is returned (title and panel list) and how real versus mock behavior is selected. It does not detail the exact panel-list structure or error cases, but those gaps are minor given the tool's low complexity. It is complete enough for an agent to invoke correctly.

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?

The input schema already has 100% description coverage for the single 'uid' parameter, including an example. The description adds only that the UID identifies a dashboard and that certain mock UIDs exist. That is minimal added meaning beyond the schema, so the baseline 3 is appropriate.

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 gives a specific verb and resource: 'Fetch a Grafana dashboard's title and panel list by UID.' This clearly distinguishes it from the Kubernetes and Prometheus siblings by domain and operation. No ambiguity about what the tool does.

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

Usage Guidelines3/5

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

The description implies when to use it by saying it fetches a dashboard summary by UID, but it does not explicitly compare against alternatives or state when not to use it. The fallback mock behavior is useful context but not usage guidance. A 3 is appropriate because the correct use is inferable but not fully outlined.

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