Skip to main content
Glama

get_recent_errors

Retrieve recent error entries from monitored log files for debugging and analysis, with optional file path filtering and result limit control.

Instructions

Get recent error analysis from monitored files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathNoOptional: specific file path to get errors from
limitNoMaximum number of recent errors to return

Implementation Reference

  • Tool schema definition in ListToolsRequestHandler, including name, description, and input schema for filePath (optional) and limit (default 10)
    {
      name: 'get_recent_errors',
      description: 'Get recent error analysis from monitored files',
      inputSchema: {
        type: 'object',
        properties: {
          filePath: {
            type: 'string',
            description: 'Optional: specific file path to get errors from'
          },
          limit: {
            type: 'number',
            default: 10,
            description: 'Maximum number of recent errors to return'
          }
        }
      }
    }
  • src/server.ts:192-194 (registration)
    Tool registration/dispatch in the CallToolRequestHandler switch statement
    case 'get_recent_errors':
      result = await this.handleGetRecentErrors(args);
      break;
  • MCP server handler for get_recent_errors tool that extracts parameters and delegates to FileWatcher.getRecentErrors
    private async handleGetRecentErrors(args: any): Promise<MCPToolResult> {
      const { filePath, limit = 10 } = args;
    
      const recentErrors = await this.fileWatcher.getRecentErrors(filePath, limit);
    
      return {
        success: true,
        data: recentErrors
      };
    }
  • Core helper function in FileWatcher class that implements the logic to retrieve recent errors from specific or all watched log files, sorting by timestamp
    async getRecentErrors(filePath?: string, limit: number = 10): Promise<LogAnalysis[]> {
      if (filePath) {
        const watchedFile = this.watchers.get(filePath);
        if (!watchedFile) {
          throw new Error(`File ${filePath} is not being watched`);
        }
        return watchedFile.errors.slice(-limit);
      }
    
      // Get recent errors from all watched files
      const allErrors: LogAnalysis[] = [];
      for (const watchedFile of this.watchers.values()) {
        allErrors.push(...watchedFile.errors);
      }
    
      // Sort by timestamp and return most recent
      return allErrors
        .sort((a, b) => b.metadata.timestamp.getTime() - a.metadata.timestamp.getTime())
        .slice(0, limit);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't add context beyond that—e.g., it doesn't mention if this is a read-only operation, what permissions are needed, how errors are formatted, or any rate limits. This leaves significant gaps for a tool that likely interacts with monitored files.

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 directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent 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 the complexity of error analysis and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'error analysis' entails, the format of returned data, or how it relates to sibling tools like 'analyze_log'. For a tool with no structured behavioral hints, more context is needed to be fully helpful.

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 both parameters ('filePath' and 'limit'). The description doesn't add any meaning beyond what the schema provides, such as explaining what 'recent' means or how errors are prioritized. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 ('recent error analysis from monitored files'), making the purpose understandable. It doesn't explicitly distinguish from siblings like 'analyze_log' or 'quick_scan', which might have overlapping functionality, so it doesn't reach the highest score for sibling differentiation.

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 'analyze_log' or 'list_watched_files'. It lacks context about prerequisites, such as whether files need to be monitored first, or exclusions, 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/ChiragPatankar/loganalyzer-mcp'

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