Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find DSNs

find_dsns
Read-only

List the DSNs (client keys) for a Sentry project, returning each key's ID, name, and DSN so an SDK can send events.

Instructions

List the DSNs (client keys) for a Sentry project: the SENTRY_DSN an SDK uses to send events. Returns each key's ID, name, and DSN.

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": {
      "projectSlug": "<projectSlug>"
    },
    "name": "find_dsns"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dsnsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description's added behavior ('Returns each key's ID, name, and DSN') largely duplicates the output schema, and it says nothing about caching despite a `fresh` parameter existing. Modest added value only.

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, front-loaded with the purpose, with the parenthetical gloss on DSN earning its place by disambiguating an acronym. 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?

An output schema exists, so return values needn't be explained, and annotations cover the read-only safety profile. The only real gap is that the `fresh`/cache-bypass behavior goes unmentioned, but for a simple list tool this is close to complete.

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%, so most parameters are documented in the schema itself, and regionUrl/organizationSlug descriptions even cross-reference find_organizations. The description adds no parameter meaning of its own, so the baseline of 3 applies.

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?

States a specific verb and resource ("List the DSNs (client keys) for a Sentry project") and then defines what a DSN actually is ("the SENTRY_DSN an SDK uses to send events"), which is non-obvious domain knowledge. The read verb distinguishes it cleanly from the sibling create_dsn.

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?

The purpose implies when you'd call it (you need a project's SDK key), but there is no explicit when-to-use or when-not-to-use guidance and no pointer to create_dsn for provisioning a new key. 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.