Skip to main content
Glama
Maneesh-Rajbhar

Enterprise Infrastructure & Metrics MCP Server

by Maneesh-Rajbhar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

analyze_local_logs

Tail and filter a log file by severity and substring within a sandboxed directory.

Instructions

Tail and optionally filter a log file. The path is resolved relative to a server-configured, sandboxed log directory -- absolute paths and '..' traversal are rejected. Supports a coarse severity filter (error_and_above / warning_and_above) and a case-insensitive substring search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payloadYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Implies read-only behavior through 'tail', but does not explicitly state that no modifications occur. No annotations are provided, so the description carries the burden.

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, concise sentence that front-loads the primary function and includes key security constraints.

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

Completeness4/5

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

Sufficient for an agent to understand the tool's purpose and constraints. Output format is not described in the description, but an output schema is provided.

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 description does not add parameter details beyond the schema, which already includes comprehensive descriptions for tail_lines, severity_filter, search_substring, and relative_log_path.

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?

Clearly states the tool's function: tailing and optionally filtering a log file. Also specifies security constraints for path resolution.

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

Usage Guidelines4/5

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

Provides clear action and scope but does not explicitly compare with sibling tools. However, the tool's purpose is self-evident for log analysis.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools