Read Minecraft log and crash report files by tailing recent lines or searching for keywords, so you can diagnose crashes and errors without loading entire large files.
Read a log or crash report (tail or search; never dumps the whole huge file).
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Relative path such as logs/latest.log | |
| tail | No | ||
| search | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It does state 'never dumps the whole huge file', which is a meaningful safety/performance guarantee, and it reveals tail/search capabilities. However, it omits default behavior when neither tail nor search is provided, how output is truncated, and any permission considerations.
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 front-loaded sentence with no filler: the verb and resource come first, the operations are parenthesized, and the key safety behavior is included. Every word earns its place.
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 3-parameter tool with no output schema and no annotations, the description is too thin. It does not state defaults, how results are bounded when tail/search are absent, or how the path relates to sibling tool list_logs. The 'never dumps the whole huge file' hint is useful but leaves major gaps.
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 only 33%; only path has a description. The description mentions 'tail or search' but does not explain what tail counts (lines? bytes?) or how search works (substring? regex? case-sensitive?). An agent cannot confidently construct correct values for these parameters based solely on the available text.
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 the specific verb 'Read' with the resource 'log or crash report', and adds the operational modes 'tail or search'. It is clearly distinct from sibling tools like list_logs (list vs read) and read_config, though it does not explicitly name a sibling.
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 this tool versus alternatives. It does not mention list_logs for discovering available logs, nor does it distinguish when diagnose or read_config would be more appropriate. The usage context is only implied by the tail/search hint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.