Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Create Dashboard Panel

create_dashboard_panel

Add a configurable panel to an existing Rootly dashboard, showing incident or alert data as a chart, table, or aggregate value with filters, grouping, and layout position.

Instructions

Creates a new dashboard panel from provided data. OAuth tokens need the ir.dashboards:write 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>",
      "data": "<data>"
    },
    "name": "create_dashboard_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=true. The description meaningfully adds that OAuth tokens require the `ir.dashboards:write` scope and that panel data is filtered by the token's other scopes, which is real behavioral context beyond the annotations.

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 action, followed by useful auth and data-visibility constraints. There is no filler, though it could be slightly tighter by grouping the two scope-related sentences.

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 annotations cover the safety profile. Still, for a create tool with a deeply nested payload, the description lacks guidance on required payload structure, panel types, and error or duplicate behavior.

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 coverage is 50%. The `dashboard_id` parameter is documented in the schema, and the description adds that panel data is limited by token scopes. However, it says nothing useful about constructing the large nested `data` object, including panel type, display, datasets, filters, or position.

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: 'Creates a new dashboard panel from provided data.' It clearly implies a create operation distinct from get_dashboard_panel and update_dashboard_panel, though it does not explicitly name those siblings.

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?

Usage is implied: create a new panel, presumably on an existing dashboard. The description adds a prerequisite, the `ir.dashboards:write` scope, but gives no explicit when-not guidance or direction to alternatives such as update_dashboard_panel or create_dashboard.

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