Retrieve and filter the current Dragon's Dogma 2 REFramework log by substring to diagnose errors or inspect specific events during a game run.
REFramework log for the current game run, optionally filtered by a substring (e.g. '[Bastion]', 'error').
| Name | Required | Description | Default |
|---|---|---|---|
| lines | No | ||
| pattern | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It identifies the scope as the current game run, but does not state whether the operation is read-only, whether results are truncated, how many lines are returned by default, or any permission or rate-limit 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 well-formed sentence with no wasted wording. The core purpose is front-loaded, and the optional filter is described immediately afterward.
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?
The tool is simple and an output schema exists, but the description still omits important details about the undocumented lines parameter, default behavior, and whether the log is truncated. For a two-parameter tool with no schema descriptions or annotations, more context is needed.
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 0%, so the description must explain both parameters. It adds useful meaning for the pattern parameter by describing substring filtering and giving examples, but it does not explain the lines parameter 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?
The description clearly states that this tool retrieves the REFramework log for the current game run and supports optional substring filtering. It is specific about the resource and operation, though it does not explicitly distinguish itself from sibling tools such as dd2_status or dd2_recent_items.
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?
The only usage guidance is that filtering is optional, with example substrings. There is no explicit statement of when to use this tool versus alternatives, nor any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.