Skip to main content
Glama
vishalzambre

Honeybadger MCP Server

by vishalzambre

list_honeybadger_faults

Fetch recent application errors from Honeybadger to analyze and troubleshoot issues directly in your development environment.

Instructions

List recent faults from Honeybadger

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoOptional project ID (uses env var if not provided)
limitNoNumber of faults to fetch (default: 20, max: 100)
environmentNoFilter by environment (e.g., production, staging)
resolvedNoFilter by resolved status

Implementation Reference

  • The primary handler function for the 'list_honeybadger_faults' tool. It extracts parameters (project_id, limit, environment, resolved), makes an authenticated API request to Honeybadger's faults endpoint, and returns the JSON response formatted as MCP content.
    private async listFaults(args: any): Promise<any> {
      const pid = args.project_id || this.config.projectId;
      if (!pid) {
        throw new McpError(ErrorCode.InvalidRequest, 'Project ID is required');
      }
    
      const params: any = {
        limit: Math.min(args.limit || 20, 100),
      };
    
      if (args.environment) params.environment = args.environment;
      if (typeof args.resolved === 'boolean') params.resolved = args.resolved;
    
      const data = await this.makeHoneybadgerRequest(`/projects/${pid}/faults`, params);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:135-161 (registration)
    Registration of the 'list_honeybadger_faults' tool in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'list_honeybadger_faults',
      description: 'List recent faults from Honeybadger',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'Optional project ID (uses env var if not provided)',
          },
          limit: {
            type: 'number',
            description: 'Number of faults to fetch (default: 20, max: 100)',
            default: 20,
          },
          environment: {
            type: 'string',
            description: 'Filter by environment (e.g., production, staging)',
          },
          resolved: {
            type: 'boolean',
            description: 'Filter by resolved status',
          },
        },
        required: [],
      },
    },
  • Input schema defining optional parameters for listing faults: project_id, limit (default 20, max 100), environment, resolved.
    inputSchema: {
      type: 'object',
      properties: {
        project_id: {
          type: 'string',
          description: 'Optional project ID (uses env var if not provided)',
        },
        limit: {
          type: 'number',
          description: 'Number of faults to fetch (default: 20, max: 100)',
          default: 20,
        },
        environment: {
          type: 'string',
          description: 'Filter by environment (e.g., production, staging)',
        },
        resolved: {
          type: 'boolean',
          description: 'Filter by resolved status',
        },
      },
      required: [],
    },
  • src/index.ts:204-205 (registration)
    Dispatch case in CallToolRequestSchema handler that routes 'list_honeybadger_faults' calls to the listFaults method.
    case 'list_honeybadger_faults':
      return await this.listFaults(args as any);
  • Shared helper method makeHoneybadgerRequest used by listFaults to perform authenticated GET requests to the Honeybadger API.
    private async makeHoneybadgerRequest(endpoint: string, params: any = {}) {
      if (!this.config.apiKey) {
        throw new McpError(ErrorCode.InvalidRequest, 'HONEYBADGER_API_KEY environment variable is required');
      }
    
      const username = this.config.apiKey;
      const password = '';
      const url = `${this.config.baseUrl}/v2${endpoint}`;
      const credentials = Buffer.from(`${username}:${password}`).toString('base64');
    
    
      try {
        const response = await axios.get(url, {
          headers: {
            'Authorization': `Basic ${credentials}`,
            'Accept': 'application/json',
          },
          params,
        });
    
        return response.data;
      } catch (error: any) {
        if (error.response) {
          throw new McpError(
            ErrorCode.InvalidRequest,
            `Honeybadger API error: ${error.response.status} - ${error.response.data?.error || error.response.statusText}`
          );
        }
        throw new McpError(ErrorCode.InternalError, `Network error: ${error.message}`);
      }
    }
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 'List recent faults' but doesn't explain what 'recent' means (e.g., time range), how results are ordered, pagination behavior, or error handling. This leaves significant gaps for a tool with 4 parameters and no output schema.

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 with the core action and resource, making it highly efficient and easy to parse.

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 tool's complexity (4 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain return values, error conditions, or behavioral traits like rate limits or authentication needs. For a list operation with filtering options, more context is needed to use it effectively.

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?

Schema description coverage is 100%, so the schema fully documents all 4 parameters. The description adds no additional parameter information beyond implying a list operation. This meets the baseline of 3, as the schema handles the heavy lifting, but the description doesn't enhance understanding of parameter interactions or defaults.

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 ('List') and resource ('recent faults from Honeybadger'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_honeybadger_fault' or 'get_honeybadger_notices', which likely retrieve specific items rather than lists.

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 sibling tools like 'analyze_honeybadger_issue' or 'get_honeybadger_fault', nor does it specify use cases or prerequisites beyond the basic action.

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