Read the UMM mod manager log file. Returns the last N lines by default, or filter by pattern.
Read the UMM mod manager log file. Returns the last N lines by default, or filter by pattern.
| Name | Required | Description | Default |
|---|---|---|---|
| lines | No | Number of lines to return from the end of the log (default: 50) | |
| filter | No | Only return lines containing this string (case-insensitive) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the default line count and filter behavior, but it does not clarify return format, error behavior, whether the filter applies before or after limiting lines, or what happens if the log file does not exist. This is a read operation, so side-effect risk is low, but the behavioral detail is thin.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, tightly written sentence with no filler. It front-loads the primary purpose and then states the two key behaviors efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with a fully documented schema, this is minimally adequate. However, the interaction between lines and filter is ambiguous—whether filtering returns the last N matching lines or filters the last N lines—and there is no mention of watch_log for continuous reading. An agent could call it, but not with full confidence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with lines and filter already documented including defaults and case-insensitivity. The description largely restates these facts and adds no extra semantic detail beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Read the UMM mod manager log file.' It also clearly states the output behavior: returns last N lines by default or filtered by pattern. It does not explicitly contrast with sibling watch_log, so it stops short of a full 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use read_log versus watch_log or any other tool. No exclusions, prerequisites, or alternative conditions are mentioned. The distinction from watch_log is only implicit in the verb 'Read.'
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.