Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_get_item_by_counter

Retrieve a specific error tracking item from Rollbar using its project counter ID to access detailed information for analysis and debugging.

Instructions

Get a specific item by project counter from Rollbar. The counter is the visible ID that appears in the Rollbar UI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
counterYesProject counter for the item

Implementation Reference

  • Handler implementation for the 'rollbar_get_item_by_counter' tool. Extracts 'counter' from arguments, checks for projectClient, makes GET request to `/item_by_counter/${counter}`, and returns JSON response.
    case "rollbar_get_item_by_counter": {
      // Project Token is required
      if (!projectClient) {
        throw new Error("ROLLBAR_PROJECT_TOKEN is not set, cannot use this API");
      }
    
      const { counter } = args as { counter: number };
      const response = await projectClient.get<ItemResponse>(`/item_by_counter/${counter}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Schema definition for the tool, including name, description, and input schema requiring a 'counter' number.
    const GET_ITEM_BY_COUNTER_TOOL: Tool = {
      name: "rollbar_get_item_by_counter",
      description:
        "Get a specific item by project counter from Rollbar. The counter is the visible ID that appears in the Rollbar UI.",
      inputSchema: {
        type: "object",
        properties: {
          counter: { type: "number", description: "Project counter for the item" },
        },
        required: ["counter"],
      },
    };
  • src/rollbar.ts:298-314 (registration)
    Registration of all tools in the ListToolsRequestHandler, including GET_ITEM_BY_COUNTER_TOOL at position for 'rollbar_get_item_by_counter'.
    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,
      ],
    }));
Behavior3/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. It describes the lookup behavior (retrieving an item by counter) but lacks details on error handling, rate limits, authentication needs, or response format. While it covers the basic operation, it misses important behavioral context for a tool without annotations.

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 clarifying detail. Every word earns its place, with no redundancy or fluff, making it highly efficient and easy to parse for an AI agent.

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's low complexity (1 parameter, no nested objects) and high schema coverage, the description is adequate but not complete. It lacks output schema, so it should ideally hint at the return type or structure. Without annotations, more behavioral details would improve completeness for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 parameter 'counter' documented as 'Project counter for the item.' The description adds value by clarifying that 'The counter is the visible ID that appears in the Rollbar UI,' providing practical context beyond the schema. This enhances understanding of where to obtain the counter value.

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'), resource ('from Rollbar'), and distinguishing feature ('by project counter'). It explicitly differentiates from siblings like 'rollbar_get_item' and 'rollbar_get_item_by_occurrence_uuid' by specifying the counter-based lookup method, making the purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives: it specifies 'by project counter' and notes that 'The counter is the visible ID that appears in the Rollbar UI,' distinguishing it from other item retrieval methods like by occurrence UUID. This helps the agent choose the correct tool based on the available identifier.

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