Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Update Onboarding Status

onboarding_status_update
Idempotent

Reports SDK setup progress to Sentry's onboarding UI for a single stage and returns whether further updates are needed, so setup runs stop when Sentry no longer expects them.

Instructions

Report progress to Sentry's agentic onboarding (getting started) UI for one stage of an SDK setup run. Use only with a run token from the Sentry getting started skill, at the stage boundaries it describes. Returns whether Sentry wants further updates; stop when it does not.

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": {
      "runToken": "<runToken>",
      "update": "<update>"
    },
    "name": "onboarding_status_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
updateYesProgress update for one onboarding stage.
runTokenYes10-character run token from the Sentry getting started skill.
regionUrlNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
continueUpdatesYesFalse when Sentry wants no further updates for this run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=true), and the description adds genuinely new behavior: the call is gated on a run token issued by another skill, must be timed to stage boundaries, and its result is a control signal that can terminate the loop. It stops short of saying what happens with an invalid/expired token or a stage-boundary violation.

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 sentences, front-loaded with purpose, then constraint, then return/stop behavior — nothing redundant and no restatement of the title. Each sentence carries a distinct decision-relevant fact.

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 and annotations are rich, so return shape and safety need little prose; the description still usefully states that the response drives whether to keep updating. What remains unstated is failure behavior (bad token, wrong stage boundary) and whether repeated identical updates are meaningful despite idempotentHint.

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% and the input schema is unusually explicit — enum values, per-stage extra fields, accumulation semantics for projectSlugs/issueIds, and credential-hygiene warnings on eventNote. The description only re-characterizes runToken and the 'one stage' constraint, so it adds little beyond what the schema already states. Baseline 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?

Names a specific verb+resource+scope: reporting progress to Sentry's agentic onboarding UI for exactly one stage of an SDK setup run. The 'onboarding (getting started) UI' framing makes clear this is not the generic CRUD 'update_*' sibling set, so an agent can rule out update_project/update_issue without reading schemas.

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?

Gives a hard precondition ('Use only with a run token from the Sentry getting started skill') and a timing rule ('at the stage boundaries it describes'), plus an explicit stopping condition ('stop when it does not [want further updates]'). No named alternative is offered, but the sibling list contains no competing progress-reporting tool, so that omission is low-cost.

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