Stop recording gameplay inputs in Godot projects to end capture sessions.
Stop input recording. (Compatibility tool)
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": "stop_recording"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| timeoutMs | No | ||
| autoConnect | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Fails to disclose what happens to the recording data upon stopping (is it saved, returned, or discarded?), the purpose of the timeout parameter, or what auto-connecting refers to.
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?
Extremely brief (4 words plus parenthetical), which is structurally efficient, but fails to earn its place by omitting critical parameter and behavioral context required due to lack of schema documentation and annotations.
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?
Inadequate for a tool with 2 parameters and no output schema. Missing parameter semantics, return value description (what does the tool return?), and behavioral details necessary for correct invocation in the recording workflow.
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 has 0% description coverage. Description completely omits explanation of `timeoutMs` (timeout for what operation?) and `autoConnect` (connect to what?), leaving both parameters semantically undocumented despite the low schema coverage.
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 the basic action (stopping input recording) and identifies it as a 'compatibility tool', but lacks specificity regarding the recording lifecycle and does not differentiate from sibling tools like `start_recording` or `replay_recording`.
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?
Provides no guidance on when to invoke this tool (e.g., only after `start_recording`), workflow prerequisites, or when to prefer alternatives. The '(Compatibility tool)' parenthetical hints at limited use cases but lacks explicit instruction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.