Skip to main content
Glama

read-log-file

Read the contents of a server log file to inspect events and diagnose issues. Optionally return only the last N lines for a quick view of recent activity.

Instructions

Read the contents of a log file from the server's logs directory. Optionally return only the last N lines.

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": {
      "filename": "<filename>"
    },
    "name": "read-log-file"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesName of the log file (e.g. 'app.log'). Must be a .log file inside the logs/ directory.
lastLinesNoIf specified, return only the last N lines of the file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses little beyond directory scoping. It does not say what happens with large files (truncation, size caps), whether a missing or non-.log file errors, permissions required, or whether output is raw text — all central for a file-read tool.

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 short sentences with the scoping constraint front-loaded and zero filler. Nothing is redundant or buried.

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?

For a two-parameter read with full schema coverage and no output schema, the core is present. However, an agent would still want to know the return shape (plain text block?) and how very large logs are handled before calling it.

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 description coverage is 100%, so both parameters are already documented, including the .log/inside-logs constraint and the exclusiveMinimum on lastLines. The description only restates the lastLines effect, adding no syntax or edge-case 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?

States a specific verb (read) and resource (log file) plus scope (the server's logs directory), which an agent can act on directly. No sibling in the list touches log files, so differentiation is implicit rather than stated, which keeps it just short of a 5.

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 phrase "Optionally return only the last N lines" hints at a tail-style read versus a full read, but never says when to prefer one over the other or when not to use the tool. Usage is implied rather than guided.

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