Skip to main content
Glama
lekt9

OpenReplay MCP Server

by lekt9

get_errors_issues

Retrieve and analyze application errors and issues with impact metrics and affected sessions to identify and prioritize debugging tasks.

Instructions

Get errors and issues with their impact and affected sessions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateNoStart date in ISO format
endDateNoEnd date in ISO format
errorTypesNoFilter by error types (js_exception, missing_resource, etc.)
minOccurrencesNoMinimum number of occurrences
groupByNoHow to group errors

Implementation Reference

  • The handler function that implements the core logic for the 'get_errors_issues' tool. Currently, it informs that JWT authentication is required.
    private async getErrorsIssues(args: any) {
      // Error analysis requires JWT authentication
      return {
        content: [
          {
            type: "text",
            text: "Error analysis is not available via API key authentication. JWT authentication is required for this feature.",
          },
        ],
      };
    }
  • The input schema defining parameters for the 'get_errors_issues' tool, including date ranges, error types, occurrence thresholds, and grouping options.
    inputSchema: {
      type: "object",
      properties: {
        startDate: { type: "string", description: "Start date in ISO format" },
        endDate: { type: "string", description: "End date in ISO format" },
        errorTypes: {
          type: "array",
          items: { type: "string" },
          description: "Filter by error types (js_exception, missing_resource, etc.)"
        },
        minOccurrences: { type: "number", description: "Minimum number of occurrences" },
        groupBy: { type: "string", enum: ["message", "stack", "url"], description: "How to group errors" }
      }
    }
  • src/index.ts:182-199 (registration)
    The tool registration entry in the listTools response, including name, description, and input schema.
    {
      name: "get_errors_issues",
      description: "Get errors and issues with their impact and affected sessions",
      inputSchema: {
        type: "object",
        properties: {
          startDate: { type: "string", description: "Start date in ISO format" },
          endDate: { type: "string", description: "End date in ISO format" },
          errorTypes: {
            type: "array",
            items: { type: "string" },
            description: "Filter by error types (js_exception, missing_resource, etc.)"
          },
          minOccurrences: { type: "number", description: "Minimum number of occurrences" },
          groupBy: { type: "string", enum: ["message", "stack", "url"], description: "How to group errors" }
        }
      }
    },
  • The dispatcher case in the CallToolRequest handler that routes calls to the getErrorsIssues method.
    case "get_errors_issues":
      return await this.getErrorsIssues(args);
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 mentions retrieving errors with 'impact and affected sessions', but does not specify whether this is a read-only operation, if it requires permissions, how results are paginated, or the format of returned data. This leaves significant gaps for a tool with multiple parameters.

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 that front-loads the core purpose without unnecessary words. It directly states what the tool does, making it easy to parse and understand 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 tool has 5 parameters, no annotations, and no output schema, the description is incomplete. It does not explain the return format, error impact details, or session linkage, leaving the agent with insufficient context to understand the full behavior and output of this tool.

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 5 parameters. The description adds no additional semantic meaning beyond implying filtering by date and error types, which is already covered in the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 resource ('errors and issues'), specifying what information is retrieved. However, it does not differentiate this tool from sibling tools like 'get_session_events' or 'get_performance_metrics', which might also involve error-related data, leaving some ambiguity about its unique scope.

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. With siblings like 'get_session_details' or 'search_sessions' that might overlap in error reporting, there is no explicit context, exclusions, or named alternatives to help an agent choose correctly.

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/lekt9/openreplay-mcp'

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