Read bounded logs from the most recently launched Godot editor session, including after exit, to inspect debug output and diagnose errors.
Read bounded logs of the most recently launched editor, including after exit.
| Name | Required | Description | Default |
|---|---|---|---|
| lineCount | No | ||
| sessionId | No | Explicit process/debug session handle; required for follow-up tools on MCP 2026-07-28 |
Changes observed during successful MCP inspections.
v0.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish this as a non-destructive read-only operation. The description adds useful behavior that logs remain available after editor exit and are bounded, but it omits session handling details or what the returned logs include.
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?
A single front-loaded sentence that wastes no words and puts the resource and scope first.
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?
Adequate for a simple read-only log tool with annotations covering safety, but it leaves gaps around lineCount behavior, sessionId usage, and how this differs from sibling diagnostic tools.
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 coverage is only 50%: sessionId is described in the schema, but lineCount is not. The description's 'bounded logs' vaguely hints at lineCount without explaining defaults, limits, or its effect, and it does not mention sessionId at all.
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?
States a specific verb and resource: reading bounded logs from the most recently launched editor. The 'including after exit' scope is clear, but it does not explicitly distinguish itself from sibling log/diagnostic tools like get_debug_output.
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?
Implies usage after launching an editor and even after it exits, which gives contextual guidance. However, it does not name alternatives such as get_debug_output or state when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.