Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find Dashboards

find_dashboards
Read-only

Search and list Sentry dashboards by title to retrieve dashboard IDs and titles for further use.

Instructions

List or search Sentry dashboards in an organization by title, returning dashboard IDs and titles. Open one with get_dashboard_details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_dashboards"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order for dashboard results.title
freshNoBypass cached reads.
limitNoMaximum number of dashboards to return.
cursorNo
regionUrlNo
titleQueryNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
dashboardsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavior by naming the returned fields (IDs and titles) and the natural next step, but it does not mention pagination behavior, the role of 'fresh' cache bypassing, or result ordering.

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?

Two short sentences, with the listing/search capability front-loaded and the follow-up tool named second. Every clause carries information and there is no filler.

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?

The tool is a read-only list operation with an output schema, and annotations cover its safety profile, so the description does not need to explain return values in detail. It is complete enough to select and invoke the tool, though it could note pagination for multi-page result sets.

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 description coverage is 57%, so several parameters (sort, fresh, limit, cursor, regionUrl) are documented in the schema itself. The description only reinforces that search is by title and that results include IDs and titles; it adds no guidance on pagination, sort order, or organization scoping beyond the schema. 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 states a specific verb ('List or search') and resource ('Sentry dashboards in an organization') with scope ('by title'), and it clarifies the return payload ('dashboard IDs and titles'). An agent can distinguish this from get_dashboard_details 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 clear context for when this tool applies (listing or title-based searching) and explicitly routes the agent to get_dashboard_details for opening a specific dashboard. It does not state exclusions, such as when to use a broader organization lookup instead, but the usage context is unambiguous.

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