Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Add Team to Project

add_team_to_project
Idempotent

Grants a Sentry team access to a project and returns the project's teams; no change is made if the team already has access.

Instructions

Grant a team access to a Sentry project. Returns the project's teams; makes no change if the team already has access.

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

Input Schema

NameRequiredDescriptionDefault
teamSlugYesThe team slug.
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
teamsYes
changedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

The description goes beyond the supplied annotations by stating two concrete behaviors: the response returns the project's teams, and the call is a no-op if the team already has access (corroborating idempotentHint=true with specifics). It stops short of disclosing permission or scope requirements for granting project access, which matters for a mutation tool with openWorldHint=true.

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 with zero filler. The action is front-loaded and the return/no-op note follows immediately; every clause earns its place.

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 two-required-parameter association tool with an output schema and rich annotations, the description covers action, return, and repeat-call behavior. The remaining gap is authorization context (what scope is needed and what happens when it's missing), which an agent calling a cross-organization grant would benefit from.

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?

The description references no parameter at all; the meaning of projectSlug, teamSlug, organizationSlug, and regionUrl comes entirely from the schema, which already covers 75% of parameters. With that coverage level, the schema does the work and the description adds nothing extra, so the 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?

"Grant a team access to a Sentry project" names a specific verb (grant access), the resource (team-to-project association), and the direction of the operation, which cleanly separates it from the sibling remove_team_from_project. An agent knows exactly what state change this tool performs.

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?

Usage is only implied by the verb phrase; there is no explicit "use this when..." or routing to find_teams/find_projects for resolving the required slugs, and no mention of when a different tool (e.g., create_team or update_project) would be appropriate instead. The only conditional offered is the no-op case when access already exists.

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