Manage Dolphin emulator memory scans: start, refine, inspect, cancel, undo, or filter scan results to locate and track target game values.
Start, refine, inspect, cancel, dispose, undo, or filter a Dolphin memory scan.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| arguments | Yes | ||
| timeoutMs | No | ||
| awaitCompletion | No |
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 implies several operations, but does not disclose side effects, which actions mutate or destroy scan data, permission requirements, whether refine depends on a prior scan, or how timeoutMs and awaitCompletion affect execution.
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?
It is a single, front-loaded sentence with no wasted words. However, for a complex action-multiplexing memory-scan tool, this level of brevity leaves the agent without enough structure to safely choose and invoke an action.
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?
Given four parameters, a nested object, zero schema description coverage, no annotations, and no output schema, the description is far too thin. It does not explain action arguments, return values, action ordering, or how the scan lifecycle is intended to be managed.
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% for four parameters, including a nested free-form arguments object and timeoutMs/awaitCompletion fields. The description's action list does not map cleanly to the action enum and supplies no semantics for arguments, timeoutMs, or awaitCompletion.
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?
It states a resource, 'Dolphin memory scan,' and lists multiple verbs, so the general domain is clear. However, the listed actions do not fully match the action enum ('inspect'/'filter' vs. 'status'/'results'/'removeResults'), and it does not distinguish this multiplexer from siblings such as dolphin_memory, dolphin_start, or dolphin_status.
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 description provides no guidance on when to use this tool versus its many dolphin_* siblings, nor any prerequisites, ordering of actions, or conditions for choosing start/refine/status/results/cancel/etc. It only lists possible operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.