Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find Organizations

find_organizations
Read-only

List or search the Sentry organizations a user can access and return their slugs and region URLs for other Sentry tools, 25 per page.

Instructions

List or search the Sentry organizations the user can access. Returns each organization's slug and region URL, which other Sentry tools take, plus its web URL; 25 per page.

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_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
queryNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
hasMoreYes
nextCursorYes
organizationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, non-destructive, so the description is not needed for safety. It still adds real behavior beyond them: access scoping to the user's organizations, the concrete return fields (slug, region URL, web URL), the fact that the slug/region URL are inputs other Sentry tools accept (chaining guidance), and pagination size.

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 sentences, no filler, and the core purpose is front-loaded before return-shape and pagination details. Every clause carries information an agent can act on.

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?

With an output schema present, return values need not be spelled out, yet the description usefully summarizes them and explains how the returned identifiers feed other tools. The only gap is the undocumented `fresh` parameter, which for a low-complexity read-only list tool is minor.

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 only 33%, so the description must compensate; it does partially by clarifying that searching filters organizations and by disclosing the 25-per-page page size that makes the cursor meaningful. It adds nothing about the `fresh` cache-bypass parameter, leaving one of three inputs explained only by its own schema text.

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?

States a specific verb pair and resource ('List or search the Sentry organizations') plus an access scope ('the user can access'). The resource is distinct from every listed sibling (projects, teams, monitors, alerts), so an agent can identify it without a named alternative, though no explicit sibling contrast is offered.

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?

'List or search' implies the two modes (no query = enumerate, query = filter), but the description never states when to prefer this over related lookups or any prerequisites/exclusions. Usage is inferable rather than stated.

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