Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_get_user

Retrieve a specific user's information from Rollbar error tracking by providing their user ID.

Instructions

Get a specific user from Rollbar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUser ID

Implementation Reference

  • The handler for the 'rollbar_get_user' tool. It checks for accountClient availability, extracts the user ID from arguments, calls the Rollbar API endpoint `/user/${id}` to fetch user data, and returns the JSON stringified response.
    case "rollbar_get_user": {
      // Account Token is required
      if (!accountClient) {
        throw new Error("ROLLBAR_ACCOUNT_TOKEN is not set, cannot use this API");
      }
    
      const { id } = args as { id: number };
      const response = await accountClient.get<UserResponse>(`/user/${id}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • The schema definition for the 'rollbar_get_user' tool, specifying the input schema that requires a numeric 'id' for the user.
    const GET_USER_TOOL: Tool = {
      name: "rollbar_get_user",
      description: "Get a specific user from Rollbar",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "number", description: "User ID" },
        },
        required: ["id"],
      },
    };
  • src/rollbar.ts:298-314 (registration)
    Registration of the 'rollbar_get_user' tool (via GET_USER_TOOL) in the list 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,
      ],
    }));
  • The 'rollbar_get_user' tool is listed in the SUPPORTED_APIS.accountApis array, used for token validation warnings.
      accountApis: ["rollbar_list_projects", "rollbar_get_project", "rollbar_list_users", "rollbar_get_user"],
    };
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 action 'Get' but doesn't describe what 'Get' entails—whether it's a read-only operation, requires authentication, returns detailed or summary data, or has any rate limits or side effects. For a tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loaded with the essential information, making it easy to parse quickly.

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 for a tool that retrieves user data. It doesn't explain what user information is returned, error conditions, or authentication requirements. While the schema covers the input parameter, the overall context for safe and effective use is insufficient, especially for a tool that likely involves sensitive user data.

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 description adds no parameter semantics beyond what the input schema provides. The schema has 100% coverage with a clear description for the 'id' parameter as 'User ID'. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate or add value but doesn't detract either.

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 the resource 'a specific user from Rollbar', which is specific and unambiguous. It distinguishes this from sibling tools like 'rollbar_list_users' by specifying retrieval of a single user rather than listing multiple users. However, it doesn't explicitly differentiate from other 'get' tools like 'rollbar_get_item' or 'rollbar_get_project' beyond the resource type.

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. It doesn't mention prerequisites like needing a user ID, when to choose this over 'rollbar_list_users', or any exclusions. The agent must infer usage from the name and context alone, which is insufficient for optimal tool selection.

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