Skip to content

Migrate low-steering tools to structuredContent #1193

Description

@sentry-junior

Master ticket for migrating data-shaped MCP tools from handwritten markdown to structuredContent + outputSchema.

Prefer tools whose handler is basically fetch → map stable fields → optional limit/cursor note, and whose only steering is presentation (“tell the user X”) or follow-up handles (slug/id/cursor). Skip tools that need markdown to make the result legible, or that return heavy untrusted telemetry.

Contract refs: docs/contributing/tool-responses.md, existing structured tools (search_ai_conversations, get_ai_conversation_details, search_sentry_tools). Related experimental work: #1045 (get_issue_details, search_events, search_issue_events).

Tier 1 — migrate first

  • find_projects — slug list; no response notes
  • find_teams — slug + id list; no response notes
  • whoami — user + optional session constraints
  • create_team — id/slug/name; drop “please tell the user the team slug” into data
  • create_dsn / find_dsns — name/id/dsn; drop “please tell the user the DSN” into data
  • update_project — small metadata echo
  • add_team_to_project / remove_team_from_project — assignment result + team list
  • find_organizations — slug, webUrl, regionUrl; region notes become fields

Tier 2 — good, more schema work

Defer

  • get_issue_details, search_events, search_issue_events, search_issues — heavy presentation + untrusted telemetry
  • get_trace_details / get_span_details, profiles, replays — big nested investigation surfaces
  • get_doc / search_docs, analyze_issue_with_seer — prose-first

Spawn child issues/PRs per tool or small batch; keep this issue as the rollup.

Requested by David Cramer via Junior.

--

View Junior Session in Sentry

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions