Skip to main content
Glama
Sign In
log-mcp

log-mcp

by ascii766164696D
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

log_overview

Scan a log file to obtain its size, line count, time range, log level distribution, and head/tail samples. Use this as the initial step in log file investigation.

Instructions

Quick scan of a log file: size, line count, time range, level distribution, and head/tail samples.

Use this as the first step when investigating a log file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "log_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
sample_linesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the outputs (size, line count, etc.) and implies read-only behavior via 'scan'. However, it does not state side effects or permissions explicitly, but for a read-like tool this is adequate.

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?

Two concise sentences with no filler. Front-loaded with the core functionality, earning every word.

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?

Given the tool's simplicity, the description is mostly complete. With an output schema present (context signal), the lack of return value detail is acceptable. Covers the basics for an overview 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 has 0% description coverage. The description mentions 'head/tail samples' hinting at sample_lines, but does not explicitly explain file_path or sample_lines. It provides some context but lacks full parameter meaning beyond the schema.

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 it provides a quick scan with metrics like size, line count, time range, level distribution, and samples. It positions itself as a first step, but does not explicitly differentiate from siblings like analyze_errors or search_logs.

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?

Explicitly says 'Use this as the first step when investigating a log file', providing clear context for when to invoke it. No mention of when not to use or alternatives, but the guidance is specific and actionable.

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