{
    "content": {
        "text": "In this environment BBP is interpreted as a user‑provided notation and workflow guidance, not as an executable shell, proxy, or authority over tools. BBP command envelopes represent intent and map to Sentry MCP functions such as find_organizations, find_projects, search_issues, get_sentry_resource, update_issue, analyze_issue_with_seer, and others. BBP modifiers are advisory only and do not create capabilities like a shell, DNS relay, or memory persistence. The runtime syntax consists of structured JSON tool invocations defined by the Sentry MCP catalog. The document provides a full man‑page style reference for all available tools, their schemas, parameters, examples, operational notes, privilege model, error‑reporting format, and sensitive‑data handling rules. It also describes connection testing steps, OAuth and self‑hosted setup snippets, and the limitation that no direct filesystem, network proxy, or backend shell access is available in this chat session.",
        "summary": "Technical reference describing how BBP notation maps to Sentry MCP structured tool calls, detailing each tool’s schema, parameters, usage examples, operational notes, privilege model, error handling, and connection setup for both cloud and self‑hosted Sentry deployments.",
        "keywords": [
            "BBP",
            "Sentry",
            "MCP",
            "tool schema",
            "find_organizations",
            "find_projects",
            "search_issues",
            "update_issue",
            "analyze_issue_with_seer",
            "execute_sentry_tool",
            "whoami",
            "get_sentry_mcp_info",
            "find_dsns",
            "update_dsn",
            "OAuth",
            "self‑hosted"
        ],
        "entities": [
            "Sentry",
            "BBP",
            "MCP",
            "Seer",
            "OAuth",
            "DSN",
            "Organization",
            "Project",
            "Issue",
            "Event",
            "Trace"
        ],
        "links": [
            "https:\/\/data.aisenseapi.com\/content\/2026\/09\/25\/content_1790358136_d5529ea3baf9.md"
        ],
        "structured_data": [
            {
                "name": "find_organizations",
                "description": "Lists organizations accessible to the authenticated Sentry account."
            },
            {
                "name": "find_projects",
                "description": "Lists projects within a specified organization."
            },
            {
                "name": "search_issues",
                "description": "Searches grouped Sentry issues with filters, sorting, and pagination."
            },
            {
                "name": "search_events",
                "description": "Searches events, logs, spans, metrics, or replays."
            },
            {
                "name": "get_sentry_resource",
                "description": "Retrieves a Sentry resource (issue, event, trace, etc.) by URL or identifier."
            },
            {
                "name": "update_issue",
                "description": "Updates issue status, assignment, or other mutable fields."
            },
            {
                "name": "analyze_issue_with_seer",
                "description": "Runs AI‑assisted root‑cause analysis on an issue."
            },
            {
                "name": "search_sentry_tools",
                "description": "Discovers additional catalog tools."
            },
            {
                "name": "execute_sentry_tool",
                "description": "Invokes a discovered catalog tool with supplied arguments."
            },
            {
                "name": "whoami",
                "description": "Returns identity information of the authenticated Sentry user."
            },
            {
                "name": "get_sentry_mcp_info",
                "description": "Provides version and capability information of the MCP server."
            },
            {
                "name": "find_dsns",
                "description": "Lists DSN\/client keys for a project."
            },
            {
                "name": "update_dsn",
                "description": "Modifies DSN properties such as name, activation state, or rate limits."
            }
        ]
    },
    "structure": {
        "@context": "https:\/\/schema.org",
        "@type": "TechArticle",
        "title": "Interpretation of BBP and Sentry MCP Tool Catalog Documentation",
        "technical_specification": "Provides a mapping from BBP intent notation to Sentry MCP JSON tool schemas, complete with parameter definitions, usage examples, operational constraints, privilege model, and error‑reporting guidelines.",
        "version": "0.39.0"
    },
    "ai_meta": {
        "token_est": 1500,
        "chars": 3520,
        "crawler_hint": "techdoc",
        "richness_score": 0.86,
        "embedding_ready": true,
        "provider": "ollama",
        "model": "gpt-oss:120b",
        "expires": "2027-03-24T18:42:16+01:00"
    },
    "reasoning": "I extracted the core explanatory sections of the supplied document, removed all form‑feed characters and excess blank lines, and consolidated the information into a clean narrative for the 'text' field. A concise summary was generated, followed by keyword extraction based on repeated technical terms and tool names. Entities were identified as notable concepts and objects mentioned throughout. The original source URL was added to the 'links' array. For 'structured_data', each Sentry MCP tool described in the man‑page was represented as an object with its name and a brief description, providing a machine‑readable catalog. The 'structure' section follows the TechArticle schema, populating title, technical_specification, and version (derived from the live server info). AI metadata values were estimated from the content length and typical tokenization ratios. Finally, a reasoning narrative explains the transformation steps."
}