Resets the emulated PlayStation 2 VM to a clean state, optionally targeting a specific processor (EE or IOP) for debugging.
Request a VM reset.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "reset"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| target | No | ee |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden but only states the action. It does not disclose side effects such as state loss, reconnection requirements, or impact on ongoing operations, which are critical for a reset tool.
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 sentence, which is concise, but it sacrifices necessary detail. It is appropriately sized for a simple tool but insufficient for the complexity of a VM reset.
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 the tool's nature (VM reset), lack of output schema, and many sibling tools, the description is incomplete. It does not explain return behavior, error conditions, or when the reset completes.
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?
The schema has one parameter 'target' with default 'ee' but the description does not explain its meaning or possible values. With 0% schema coverage, the description must compensate, but it adds no parameter information.
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 'Request a VM reset' clearly identifies the action and resource, but lacks specificity about the type of reset (e.g., soft vs hard) or implications. It is not a tautology, but it is minimal.
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?
No usage guidance is provided. The description does not mention when to use reset versus sibling tools like 'resume' or 'step', nor does it specify any prerequisites or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.