Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find Projects

find_projects
Read-only

Lists or searches Sentry projects in an organization, returning project slugs in pages of 25. Use it to find a project by name, slug, or numeric ID.

Instructions

List or search projects in a Sentry organization. Returns project slugs, 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_projects"
  }
}

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
hasMoreYes
projectsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds the pagination behavior ('25 per page'), which is genuinely useful context not present in the annotations. It stops short of describing caching implications of the 'fresh' flag or how open-world/region routing behaves.

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, zero waste, with the core action front-loaded and the payout/pagination detail second. Nothing is padded or repeated from the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool takes five parameters, none required, and has an output schema plus read-only annotations, yet the description never clarifies what happens when organizationSlug or regionUrl is omitted, or that a numeric query is treated as a project ID. For a tool with a 'fresh' cache flag and region routing, that leaves meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%, so the description should compensate, but it adds meaning only for pagination (implying cursor) and says nothing about query filtering forms, the fresh/cache-bypass flag, or regionUrl behavior. The one clue it gives is that results come back as slugs, which at least hints at what query matches against.

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 gives a concrete verb pair and resource: 'List or search projects in a Sentry organization', with the return payload named ('project slugs'). It is clearly distinguishable from mutation siblings like create_project, though it does not explicitly name an alternative read tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus alternatives (e.g. find_organizations for org discovery, or any project-specific tool), nor prerequisites such as resolving organizationSlug first. The only usage signal is the word 'search', which implies the query parameter exists but doesn't say how to use it.

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