Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Dashboard Panels

list_dashboard_panels
Read-only

Retrieve the panels configured on a specific Rootly dashboard by dashboard ID; returned panel records depend on the token’s granted scopes.

Instructions

List dashboard panels. OAuth tokens need the ir.dashboards:read scope. Panel data only includes records the token's other scopes allow (e.g. ir.incidents:read, oc.alerts:read).

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": {
      "dashboard_id": "<dashboard_id>"
    },
    "name": "list_dashboard_panels"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNo
page_sizeNo
page_numberNo
dashboard_idYesRequired. ID of the dashboard (fills `{dashboard_id}` in /v1/dashboards/{dashboard_id}/panels).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the required `ir.dashboards:read` scope and the fact that returned panel records are filtered by the token's other scopes, which an agent could not infer from annotations or schema.

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?

Three short sentences, front-loaded with the purpose and then the auth constraint, with no filler. It is efficient, though the auth detail takes space that could have carried parameter guidance.

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?

An output schema exists, so return values need not be explained, and the scope/filtering caveat is valuable. However, with three of four parameters undocumented, the definition is not complete enough for an agent to call it confidently with pagination or an `include` value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: dashboard_id is documented, but `include`, `page_size`, and `page_number` have no descriptions anywhere. The description adds no meaning for those three parameters, so the agent is left guessing about accepted values, pagination defaults, and what `include` expands.

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 states a specific verb and resource ('List dashboard panels'), which is distinguishable from the single-panel sibling get_dashboard_panel and from list_dashboards. It stops short of explicitly contrasting itself with those siblings, but the scope is unambiguous.

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?

There is no guidance on when to choose this over list_dashboards or get_dashboard_panel, nor any prerequisites beyond OAuth scope. The scope sentence is an auth requirement, not usage guidance, so the agent must infer selection from the tool name alone.

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

Deploy Server

Other Tools