Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_get_occurrence

Retrieve a specific error occurrence from Rollbar using its unique ID to analyze error details and debug issues.

Instructions

Get a specific occurrence of an error from Rollbar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOccurrence ID

Implementation Reference

  • Handler function that executes the rollbar_get_occurrence tool by calling the Rollbar API to fetch a specific occurrence by its ID using the projectClient.
    case "rollbar_get_occurrence": {
      // Project Token is required
      if (!projectClient) {
        throw new Error("ROLLBAR_PROJECT_TOKEN is not set, cannot use this API");
      }
    
      const { id } = args as { id: string };
      const response = await projectClient.get<OccurrenceResponse>(`/instance/${id}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Schema definition for the rollbar_get_occurrence tool, specifying the input parameters and description.
    const GET_OCCURRENCE_TOOL: Tool = {
      name: "rollbar_get_occurrence",
      description: "Get a specific occurrence of an error from Rollbar",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "string", description: "Occurrence ID" },
        },
        required: ["id"],
      },
    };
  • src/rollbar.ts:298-314 (registration)
    Registration of the rollbar_get_occurrence tool (via GET_OCCURRENCE_TOOL) in the listTools request handler, making it available to clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        LIST_ITEMS_TOOL,
        GET_ITEM_TOOL,
        GET_ITEM_BY_UUID_TOOL,
        GET_ITEM_BY_COUNTER_TOOL,
        LIST_OCCURRENCES_TOOL,
        GET_OCCURRENCE_TOOL,
        LIST_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        LIST_ENVIRONMENTS_TOOL,
        LIST_USERS_TOOL,
        GET_USER_TOOL,
        LIST_DEPLOYS_TOOL,
        GET_DEPLOY_TOOL,
      ],
    }));
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Get') but does not specify whether this is a read-only operation, if it requires authentication, what error handling occurs, or the format of the returned data. This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and efficiently communicates the core function, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not address behavioral aspects like safety, authentication, or response format, which are crucial for a tool that retrieves error data. This leaves the agent with insufficient context to use the tool effectively.

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 input schema has 100% description coverage, with the 'id' parameter clearly documented as 'Occurrence ID'. The description does not add any additional meaning or context beyond what the schema provides, such as explaining the format or source of the ID. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('a specific occurrence of an error from Rollbar'), making the purpose unambiguous. However, it does not explicitly differentiate this tool from its sibling 'rollbar_get_item_by_occurrence_uuid', which might retrieve similar data, so it falls short of a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'rollbar_get_item' or 'rollbar_list_occurrences'. It lacks context about prerequisites, such as needing an occurrence ID, and does not mention any exclusions or specific scenarios for its use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hiyorineko/mcp-rollbar-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server