Opsphere — DevOps & SRE Intelligence

Sentry Project Stats

sentry_projects_stats

Read-only

Project received-event volume time series (GET /projects/{org}/{project}/stats/). Not release adoption — use sentry_sessions_by_release for Release Health session share by release.

Input Schema

Name	Required	Description
`since`	No	Fecha de inicio (ISO 8601, por defecto: 30 días atrás)
`until`	No	Fecha de fin (ISO 8601, por defecto: ahora)
`period`	No	Relative period, e.g. 1h, 24h, 7d
`orgSlug`	No	Organization slug; resolved from workspace defaults when omitted
`projectId`	No	Numeric Sentry project id (same as Release Health sessions tools)
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`projectSlug`	No	Project slug; resolved from workspace defaults or a sole accessible project
`statsPeriod`	No	Alias of period for Sentry compatibility

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A4/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=false, so the safety profile is covered. The description adds the endpoint shape and a scope exclusion, but says nothing about time-series resolution, bucketing, or default window behavior beyond what the schema documents.

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 sentences, zero filler, and the primary identification is front-loaded before the negative scoping guidance.

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 read-only stats query with a full output schema and fully documented parameters, the description covers what the tool returns conceptually and what it is not. Minor gap: no mention of aggregation granularity or how the time series is bucketed.

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 100% across all 8 parameters, including defaults, period formats, and workspace resolution rules, so the schema carries the burden. The description contributes no additional parameter semantics, which is the expected baseline of 3 here.

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 resource and metric (project received-event volume time series) and pins the underlying endpoint GET /projects/{org}/{project}/stats/. It also names the sibling it is not (sentry_sessions_by_release), so an agent can distinguish it without opening a schema.

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?

Explicitly routes release-adoption questions to sentry_sessions_by_release, giving a clear when-not condition. It does not, however, contrast with other Sentry read tools such as sentry_events_search or sentry_issues_list, so the routing is only partially complete.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?