Execute a single guest instruction and halt. Enables precise step-by-step debugging of emulated code.
Single-step one guest instruction and stop again.
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": "step"
}
}| 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?
No annotations exist, so the description must carry full burden. It only states that it steps one instruction and stops, without disclosing side effects like triggering breakpoints, altering trace state, or permission requirements, which is insufficient for a debugger 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 extremely concise (one sentence), but conciseness should not come at the cost of essential information. It is front-loaded but omits critical details, making it merely adequate.
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 stepping tool with 1 undocumented parameter and no output schema or annotations, the description fails to cover return values, error states, or behavior during breakpoints, leaving significant gaps for the agent.
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 only parameter 'target' is undocumented in both schema (0% coverage) and description. The default 'ee' is not explained, nor are valid values; the description adds zero meaning beyond the schema.
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 the verb 'single-step' and resource 'guest instruction', and the phrase 'stop again' indicates the tool halts after one step, distinguishing it from siblings like 'resume' (continuous execution) and 'frame_advance' (advance a frame).
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 guidance on when to use this tool versus alternatives like 'resume' or 'frame_advance'; no prerequisites or context for use are provided, leaving the agent to infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.