Skip to main content
Glama
Fato07
by Fato07

log_analyzer_extract_errors

Read-onlyIdempotent

Extract errors and exceptions from log files with stack traces. Group similar errors, include warnings if needed, and get output in markdown or JSON format.

Instructions

Extract all errors and exceptions from a log file with stack traces.

Args:
    file_path: Path to the log file
    include_warnings: Include WARN level entries (default: False)
    group_similar: Group similar error messages (default: True)
    max_errors: Maximum errors to return (1-500, default: 100)
    response_format: Output format - 'markdown' or 'json'

Returns:
    Extracted errors grouped by similarity with occurrence counts,
    timestamps, and sample stack traces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
include_warningsNo
group_similarNo
max_errorsNo
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true. The description adds useful behavioral details: grouping similar errors, returning counts/timestamps/samples. No contradictions.

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?

Concise docstring-style description with args and returns sections. No wasted words; every sentence provides necessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, 0% schema coverage, and an output schema exists, the description fully covers behavior and return details (grouped errors with counts, timestamps, samples). Complete enough for agent to use correctly.

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?

Schema coverage is 0%, but the description explains each parameter: file_path path, include_warnings default and meaning, group_similar behavior, max_errors range, and response_format options. Adds significant value beyond schema titles and defaults.

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?

Description clearly states 'Extract all errors and exceptions from a log file with stack traces,' which is a specific verb and resource. It distinguishes from sibling tools like log_analyzer_search and log_analyzer_parse.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives or provide exclusions. Usage is implied by the purpose but not guided.

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/Fato07/log-analyzer-mcp'

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