Skip to main content
Glama
vishalzambre

Honeybadger MCP Server

by vishalzambre

get_honeybadger_notices

Fetch error occurrences for a specific fault in Honeybadger to analyze and troubleshoot application issues directly from your development environment.

Instructions

Fetch notices (occurrences) for a specific fault

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fault_idYesThe ID of the fault to fetch notices for
project_idNoOptional project ID (uses env var if not provided)
limitNoNumber of notices to fetch (default: 10, max: 100)

Implementation Reference

  • The handler function that executes the 'get_honeybadger_notices' tool. It fetches notices for a given fault ID from the Honeybadger API using the configured project ID, applies a limit, and returns the JSON response formatted as MCP tool content.
    private async getNotices(faultId: string, projectId?: string, limit: number = 10): Promise<any> {
      const pid = projectId || this.config.projectId;
      if (!pid) {
        throw new McpError(ErrorCode.InvalidRequest, 'Project ID is required');
      }
    
      const data = await this.makeHoneybadgerRequest(`/projects/${pid}/faults/${faultId}/notices`, {
        limit: Math.min(limit, 100),
      });
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:112-134 (registration)
    Tool registration in the ListTools response, including name, description, and input schema definition.
    {
      name: 'get_honeybadger_notices',
      description: 'Fetch notices (occurrences) for a specific fault',
      inputSchema: {
        type: 'object',
        properties: {
          fault_id: {
            type: 'string',
            description: 'The ID of the fault to fetch notices for',
          },
          project_id: {
            type: 'string',
            description: 'Optional project ID (uses env var if not provided)',
          },
          limit: {
            type: 'number',
            description: 'Number of notices to fetch (default: 10, max: 100)',
            default: 10,
          },
        },
        required: ['fault_id'],
      },
    },
  • src/index.ts:201-202 (registration)
    Dispatch case in the CallToolRequest handler that routes the tool invocation to the getNotices method.
    case 'get_honeybadger_notices':
      return await this.getNotices(args.fault_id as string, args.project_id as string | undefined, args.limit as number | undefined);
  • Input schema properties for the tool, defining parameters like fault_id, project_id, and limit.
      limit: {
        type: 'number',
        description: 'Number of notices to fetch (default: 10, max: 100)',
        default: 10,
      },
    },
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 ('Fetch') but does not cover critical aspects like whether this is a read-only operation, potential rate limits, authentication needs, error handling, or what the return format looks like (e.g., pagination, structure). This leaves significant gaps for a tool with no annotation support.

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, direct sentence that efficiently conveys the core purpose without any redundant or unnecessary information. It is front-loaded and appropriately sized for the tool's complexity.

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 no output schema, the description is incomplete. It does not address behavioral traits (e.g., safety, performance) or explain what the tool returns, which is critical for a tool with three parameters and no structured output documentation. The high schema coverage is insufficient to compensate for these gaps.

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 input schema has 100% description coverage, clearly documenting all three parameters (fault_id, project_id, limit) with their purposes, optionality, and defaults. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating 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 ('Fetch') and resource ('notices (occurrences) for a specific fault'), distinguishing it from sibling tools like 'get_honeybadger_fault' (which fetches fault details) and 'list_honeybadger_faults' (which lists faults). It precisely defines the scope of the operation.

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 does not mention sibling tools like 'analyze_honeybadger_issue' or explain scenarios where fetching notices is appropriate versus other operations, leaving the agent without contextual usage cues.

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/vishalzambre/honeybadger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server