Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_get_item_by_occurrence_uuid

Retrieve a specific error item in Rollbar by providing its occurrence UUID to analyze and troubleshoot issues directly from error tracking data.

Instructions

Get a specific item (error) from Rollbar using an occurrence UUID. The UUID must be from an occurrence that belongs to the item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesOccurrence UUID

Implementation Reference

  • The switch case handler that destructures the 'uuid' argument from the tool call, checks for projectClient availability, makes a GET request to Rollbar API endpoint `/item/${uuid}` to fetch the item, and returns the response data as text content.
    case "rollbar_get_item_by_occurrence_uuid": {
      // Project Token is required
      if (!projectClient) {
        throw new Error("ROLLBAR_PROJECT_TOKEN is not set, cannot use this API");
      }
    
      const { uuid } = args as { uuid: string };
      const response = await projectClient.get<ItemResponse>(`/item/${uuid}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and inputSchema that requires a 'uuid' string parameter.
    const GET_ITEM_BY_UUID_TOOL: Tool = {
      name: "rollbar_get_item_by_occurrence_uuid",
      description:
        "Get a specific item (error) from Rollbar using an occurrence UUID. The UUID must be from an occurrence that belongs to the item.",
      inputSchema: {
        type: "object",
        properties: {
          uuid: { type: "string", description: "Occurrence UUID" },
        },
        required: ["uuid"],
      },
    };
  • src/rollbar.ts:298-314 (registration)
    Registers the tool by including GET_ITEM_BY_UUID_TOOL in the array of tools returned by the ListToolsRequestSchema handler.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves an item but does not describe what an 'item' entails (e.g., error details, metadata), potential errors (e.g., invalid UUID), authentication needs, rate limits, or response format. For a read operation with no annotation coverage, this leaves significant gaps in understanding 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 two sentences, front-loaded with the core purpose and followed by a constraint. Every sentence earns its place by clarifying the tool's use and prerequisite, with zero waste or redundancy.

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

Completeness3/5

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

Given the tool has one parameter with full schema coverage and no output schema, the description adequately covers the basic purpose and usage. However, it lacks details on what an 'item' contains, error handling, or other behavioral aspects, which are important for a tool with no annotations. It meets minimum viability but has clear gaps in completeness.

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%, with the parameter 'uuid' documented as 'Occurrence UUID'. The description adds minimal value beyond the schema by reiterating the UUID must be from an occurrence belonging to the item, but does not provide additional semantics like format examples or constraints. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the specific action ('Get a specific item (error) from Rollbar') and resource ('using an occurrence UUID'), distinguishing it from sibling tools like rollbar_get_item (which likely uses a different identifier) and rollbar_get_occurrence (which retrieves occurrences rather than items). It explicitly mentions the UUID must be from an occurrence belonging to the item, adding precision.

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?

The description provides clear context on when to use this tool: when you have an occurrence UUID and need the associated item. However, it does not explicitly state when not to use it or name alternatives (e.g., rollbar_get_item for item IDs), though the sibling tool names imply differentiation. The guidance is sufficient but lacks explicit exclusions.

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