Skip to main content
Glama
Fato07
by Fato07

log_analyzer_tail

Read-onlyIdempotent

Retrieve the most recent log entries from a file. Filter by severity (ERROR, WARN, INFO, DEBUG) and choose output as markdown or JSON. Default returns the last 100 lines.

Instructions

Get the most recent log entries from a file.

Args:
    file_path: Path to the log file
    lines: Number of lines to return (1-1000, default: 100)
    level_filter: Filter by log level (ERROR, WARN, INFO, DEBUG)
    response_format: Output format - 'markdown' or 'json'

Returns:
    The last N log entries, parsed and formatted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
linesNo
level_filterNo
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint true and idempotentHint true, so the description does not need to reiterate safety. It adds value by stating the output is parsed and formatted, but does not cover potential edge cases like missing files or large file handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with a one-sentence purpose followed by a structured list of parameters and return value. Every sentence is informative, though the returns section could be slightly more detailed.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the essential parameter and return details but lacks context on error handling, file accessibility, or format assumptions. While an output schema exists, the description should still mention potential issues for a comprehensive understanding.

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?

With 0% schema description coverage, the description provides meaningful explanations for all four parameters, including constraints (e.g., lines 1-1000, level filter values, output formats). This compensates for the empty schema and helps the agent understand valid inputs.

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 tool retrieves the most recent log entries from a file, which directly addresses its purpose. It implies a tail-like behavior, but does not explicitly differentiate from sibling tools like search or watch, which could lead to ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any preconditions, exclusions, or scenarios where other sibling tools would be more appropriate, leaving the AI agent without decision support.

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