Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Create DSN

create_dsn

Create an additional DSN (client key) for an existing Sentry project, including a separate production key, and return its ID, name, and DSN.

Instructions

Create an additional DSN (client key) for an existing Sentry project, such as a separate production key. Returns the new key's ID, name, and DSN. create_project already provisions a DSN for a new project.

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": "<name>"
    },
    "name": "create_dsn"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesKey name, such as `Production`.
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
dsnYes

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?

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write-but-non-destructive profile is covered. The description adds only that the new key's ID, name, and DSN are returned, which duplicates the output schema and says nothing about required permissions, key limits per project, or whether the DSN is immediately active.

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?

Three short sentences, front-loaded with the action and scope, followed by the concrete example and the sibling disambiguation. Nothing is redundant or padded.

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?

For a create operation with an output schema, the description covers purpose, scope, and the key sibling distinction, which is enough to select and call it correctly. Minor gaps — permission requirements and whether multiple keys can coexist under the same name — keep it from a 5.

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 75%, with all four parameters documented in the schema itself, including the org/project slug split and the regionUrl fallback for self-hosted instances. The description adds no parameter-level meaning beyond that, 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?

The description names a specific verb and resource ("Create an additional DSN (client key)"), narrows the scope with "for an existing Sentry project," and gives a concrete example use case ("a separate production key"). The closing sentence explicitly separates it from create_project, which already provisions a DSN for new projects.

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 states the condition for use — an existing project that needs an extra key — and rules out the closest confusion by noting create_project already handles the new-project case. It does not explicitly address update_dsn or find_dsns, but the "additional" framing implies this is for net-new keys rather than modifications.

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