Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_get_deploy

Retrieve specific deployment details from Rollbar error tracking to monitor release status and analyze deployment impact.

Instructions

Get a specific deploy from Rollbar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployIdYesDeploy ID

Implementation Reference

  • The switch case handler for 'rollbar_get_deploy' that checks for projectClient, extracts deployId from arguments, calls the Rollbar API endpoint `/deploy/${deployId}`, and returns the response as formatted JSON text.
    case "rollbar_get_deploy": {
      // Project Token is required
      if (!projectClient) {
        throw new Error("ROLLBAR_PROJECT_TOKEN is not set, cannot use this API");
      }
    
      const { deployId } = args as { deployId: number };
      const response = await projectClient.get<DeployResponse>(`/deploy/${deployId}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • The Tool object definition providing the name, description, and inputSchema (requiring deployId as number) for the rollbar_get_deploy tool.
    const GET_DEPLOY_TOOL: Tool = {
      name: "rollbar_get_deploy",
      description: "Get a specific deploy from Rollbar",
      inputSchema: {
        type: "object",
        properties: {
          deployId: { type: "number", description: "Deploy ID" },
        },
        required: ["deployId"],
      },
    };
  • src/rollbar.ts:298-314 (registration)
    Registration of the rollbar_get_deploy tool (as GET_DEPLOY_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 tool name is listed in the SUPPORTED_APIS.projectApis array used for token validation warnings.
      "rollbar_get_deploy",
    ],
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Get' but doesn't clarify if this is a read-only operation, what data is returned, error handling, or any constraints (e.g., authentication, rate limits). This leaves significant gaps for a tool that likely interacts with an external API.

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 with zero waste. It's front-loaded and efficiently conveys the core action without unnecessary elaboration, 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 no annotations and no output schema, the description is incomplete for a tool that likely returns structured data. It doesn't explain what a 'deploy' entails, the response format, or any behavioral traits, leaving the agent under-informed about how to use it effectively in context.

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 'deployId' documented as 'Deploy ID'. The description adds no parameter details beyond this, but with high schema coverage and only one parameter, the baseline is strong. A 4 reflects that the schema adequately handles semantics, though the description doesn't enhance it.

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

Purpose3/5

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

The description 'Get a specific deploy from Rollbar' clearly states the verb ('Get') and resource ('deploy'), but it's vague about what 'get' entails (e.g., retrieve metadata, fetch details) and doesn't distinguish it from sibling tools like 'rollbar_list_deploys' or 'rollbar_get_item'. It's functional but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a deploy ID), exclusions, or how it differs from list or other get tools, leaving the agent to infer usage from the name alone.

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