Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Who Am I

whoami
Read-only

Identify the authenticated Sentry user by returning their name and email, with an option to bypass cached reads for current account details.

Instructions

Identify the authenticated Sentry user: name and email.

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": "whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.

Output Schema

NameRequiredDescriptionDefault
userYes
accountsNo
sessionConstraintsYes

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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the scope constraint that it only resolves the *authenticated* user (no user lookup parameter), which is useful. However it says nothing about the cached-read behavior implied by the 'fresh' parameter, which is the one behavioral trait worth disclosing.

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?

One front-loaded sentence with no filler; the resource and return fields are stated up front and nothing is repeated from the name or title.

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-value explanation is not required, and annotations cover the safety profile. The only shortfall is the absent mention of caching/staleness behavior, which matters slightly for an identity check performed mid-workflow.

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 100% and the single 'fresh' parameter is fully documented in the schema ('Bypass cached reads.'). The description adds no parameter-level meaning, which is the expected baseline when the schema does the work.

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 ('Identify') and resource ('the authenticated Sentry user') and even names the returned fields (name and email). No sibling tool does authenticated-identity lookup, so an agent can route this without opening the schema.

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?

There is no explicit when-to-use or when-not-to-use statement, but the purpose strongly implies the only sensible trigger: needing to know which account the current credentials belong to. For a single-parameter identity probe, this implied usage is adequate, though zero guidance is given about calling it before user-scoped operations.

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