Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_get_project

Retrieve project details from Rollbar error tracking by specifying the project ID to access configuration, settings, and metadata.

Instructions

Get a specific project from Rollbar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject ID

Implementation Reference

  • Handler implementation for the 'rollbar_get_project' tool. Fetches project details from Rollbar API using the account client and effective project ID.
    case "rollbar_get_project": {
      // 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 };
    
      // Use environment variable project ID as default value, or search by project name
      const effectiveProjectId = await getEffectiveProjectId(id);
    
      if (!effectiveProjectId) {
        throw new Error("Project ID is required but not provided in request or environment variables");
      }
    
      const response = await accountClient.get<ProjectResponse>(`/project/${effectiveProjectId}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Tool schema for 'rollbar_get_project' defining the input schema requiring a project 'id'.
    const GET_PROJECT_TOOL: Tool = {
      name: "rollbar_get_project",
      description: "Get a specific project from Rollbar",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "number", description: "Project ID" },
        },
        required: ["id"],
      },
    };
  • src/rollbar.ts:298-314 (registration)
    Registration of the 'rollbar_get_project' tool (as GET_PROJECT_TOOL) in the listTools request 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,
      ],
    }));
  • Helper function 'getEffectiveProjectId' used by the handler to resolve the project ID from args, env vars, or project name search.
    const getEffectiveProjectId = async (providedId?: number): Promise<number | undefined> => {
      // Use provided ID if available
      if (providedId) return providedId;
    
      // Use project ID from environment variable if available
      if (ROLLBAR_PROJECT_ID) return ROLLBAR_PROJECT_ID;
    
      // Search by project name
      if (ROLLBAR_PROJECT_NAME) {
        const idFromName = await findProjectIdByName(ROLLBAR_PROJECT_NAME);
        if (idFromName) return idFromName;
      }
    
      return undefined;
    };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error handling, or what happens if the project ID doesn't exist. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 perfectly concise - a single sentence that communicates the essential purpose without any wasted words. It's front-loaded with the core functionality and doesn't include unnecessary elaboration.

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?

For a read operation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information is returned about the project, what format the response takes, or any limitations of the retrieval. Given the lack of structured data elsewhere, the description should provide more contextual information.

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 doesn't add any parameter information beyond what's already in the schema, which has 100% coverage and clearly documents the single 'id' parameter as a Project ID. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description adds no additional context about parameter usage or constraints.

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 action ('Get') and resource ('a specific project from Rollbar'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'rollbar_list_projects' which retrieves multiple projects versus this tool's single-project retrieval, preventing 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_list_projects' for listing multiple projects or other 'rollbar_get_*' tools for different resource types. It lacks any context about prerequisites, error conditions, or typical use cases.

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