Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Dashboard Details

get_dashboard_details
Read-only

Retrieve a Sentry dashboard by numeric ID or exact title, including widget saved queries, transformations, projects, environments, filters, and layout; returns saved definitions, not live widget data.

Instructions

Get one Sentry dashboard by numeric ID or exact title: its widgets with saved query definitions and transformations, projects, environments, filters, and layout. Returns saved queries, not live widget data. To find a dashboard, use find_dashboards.

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": {
      "dashboardIdOrTitle": "<dashboardIdOrTitle>"
    },
    "name": "get_dashboard_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
regionUrlNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.
dashboardIdOrTitleYesThe dashboard's numeric ID or exact title; a title must match exactly one dashboard, ignoring case.

Output Schema

NameRequiredDescriptionDefault
dashboardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the result is the saved configuration ("Returns saved queries, not live widget data"), which prevents an agent from expecting live metrics, and it notes title matching is exact and case-insensitive with an implicit uniqueness requirement.

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?

Three short sentences, front-loaded with the core action and payload, then the key behavioral caveat, then the sibling routing hint. Nothing is redundant with the schema or annotations, and no sentence could be dropped without losing information.

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?

An output schema exists, so return-structure explanation is not required, and annotations cover side-effect behavior. The description still supplies the one thing structured fields cannot: the saved-vs-live distinction and the routing alternative. Only minor gaps remain, such as behavior when a title matches zero or multiple dashboards.

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 75%, with the key parameter dashboardIdOrTitle already documented in detail (numeric ID or exact title, case-insensitive, must match exactly one). The description restates that lookup mode but adds no syntax or constraints for the remaining parameters (fresh, regionUrl, organizationSlug), all of which are documented only in the schema. Baseline 3 is appropriate given the schema does most of the work.

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 states a specific verb and resource ("Get one Sentry dashboard") and then enumerates exactly what the payload contains: widgets with saved query definitions and transformations, projects, environments, filters, and layout. It also explicitly distinguishes itself from the sibling find_dashboards, so an agent can tell the two apart without opening either schema.

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?

It gives explicit routing guidance for the main ambiguity: "To find a dashboard, use find_dashboards," which tells the agent when to pick the sibling instead. It does not discuss conditions around the secondary parameters (fresh, regionUrl) or when a title lookup might be ambiguous, so it stops short of full when/when-not coverage.

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