Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find Teams

find_teams
Read-only

List or search teams in a Sentry organization by name or slug, returning each team's slug and numeric ID, 25 per page.

Instructions

List or search teams in a Sentry organization. Returns each team's slug and numeric ID, 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_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
queryNo
cursorNo
regionUrlNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
teamsYes
hasMoreYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/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 genuinely useful behavior not in the annotations: results are paginated at 25 per page, which signals the caller may need to iterate. The stated return fields (slug, numeric ID) are largely redundant given an output schema exists.

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 purpose front-loaded and the pagination/return detail second. No filler or redundant restatement of the tool name.

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?

For a read-only list tool with an output schema and annotations, the description covers purpose and pagination adequately, so return values need not be explained. However, it omits the organization-scoping prerequisite (organizationSlug/regionUrl sourcing) and gives no hint about cache bypass via fresh, leaving meaningful gaps for a 5-parameter tool.

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 reported at 40%, so the description should compensate more than it does. It implies the query filter ('search') and cursor pagination ('25 per page'), but says nothing about fresh, regionUrl, or organizationSlug, and never states that the organization must be resolved via find_organizations first.

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 uses a specific verb and resource ('List or search teams in a Sentry organization') and states the returned fields, so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from siblings, though the read-vs-create split with create_team is self-evident from the name.

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 = full list, query = filtered), which is adequate implied guidance. There is no explicit statement of when to prefer this over alternatives or of prerequisites such as needing the organization slug first.

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