Disconnect from the Godot engine bridge to terminate the active WebSocket connection and end AI control sessions.
Disconnect from the Godot bridge.
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": "godot_disconnect"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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. States the action but omits side effects: whether this stops running scenes, clears editor state, requires confirmation, or can be reversed by reconnecting. 'Disconnect' implies termination but lacks safety context.
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?
Single sentence is appropriately brief for a zero-parameter tool. Front-loaded with the core action. Slightly redundant with tool name but 'Godot bridge' adds specificity beyond 'godot_disconnect'.
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?
Adequate for a simple disconnect tool but minimal. Given lack of annotations and output schema, description should mention whether this affects running game instances or editor state. Minimum viable coverage.
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?
Input schema has zero parameters. According to scoring rules, 0 params = baseline 4. No parameter information needed or provided.
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?
Specific verb ('Disconnect') + resource ('Godot bridge') clearly stated. Distinguishes from sibling tool 'godot_connect' by describing the inverse operation.
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 versus staying connected, or prerequisites (e.g., whether godot_connect must be called first). No mention of cleanup requirements before disconnection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.