Skip to main content
Glama

Monitoring dashboards

monitoring_dashboards
Read-only

The dashboards of a project's monitoring (get_monitoring) — by words of their titles — each with its uid, folder, tags and link; or, with 'dashboard' (a uid), that dashboard's panels with the PromQL behind each, which is what monitoring_query is best asked with. For the people who work in the project and the company; at most 60 reads of a project's monitoring an hour, agents and people together. A refusal has a 'state': not_connected (with the 'url' of the screen that connects one), off, refused, sealed, unreachable, busy, too_big, missing, no_access, not_found, bad_request.

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": {
      "project": "<project>"
    },
    "name": "monitoring_dashboards"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoWords of a dashboard's title.
projectYesProject key, e.g. 'PM'.
dashboardNoOne dashboard's uid, for its panels and their queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, yet the description adds real behavior: a 60-reads-per-project-per-hour limit shared by agents and people, plus a full enumeration of refusal 'state' values including not_connected with a connect URL. That is exactly the context annotations cannot carry; the one gap is it doesn't say how results are paginated or bounded.

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

Conciseness3/5

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

Front-loads the two modes well, but the prose is packed into semicolon- and em-dash-chained clauses, and 'For the people who work in the project and the company' is ambiguous padding. The long error-state enumeration is useful but contributes to an overstuffed single paragraph.

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?

Very complete on failure modes, rate limits, and the shape of both return variants, so an agent can act and handle refusals. However, no output schema exists and the description never says whether panel/query results can be truncated or how to page past the 60-read ceiling.

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?

Schema description coverage is already 100%, so the baseline is 3; the description earns a bump by tying each param to an outcome — 'search' scopes by title words and yields the dashboard list, 'dashboard' takes a uid and switches to panels plus PromQL, and 'project' is implied as the scoping key. It adds consequence, not just restated field text.

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?

States two concrete modes with verb+resource: listing a project's monitoring dashboards by title words (returning uid, folder, tags, link), or fetching one dashboard's panels and their PromQL via a uid. It also names its parent tool get_monitoring, so an agent can place it precisely in the family.

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

Usage Guidelines4/5

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

Explicitly routes query work to monitoring_query ('which is what monitoring_query is best asked with') and frames this tool as the dashboard/panel accessor under get_monitoring. It stops short of stating hard exclusions (e.g., when to prefer monitoring_alerts or monitoring_hosts), but the mode split is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources