Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

simulate_mouse_click

Simulates mouse button press or release at a screen position in the running Godot game, enabling automated input testing and interactions.

Instructions

Simulate a mouse button click in the running game.

Tool call template

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": "simulate_mouse_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
buttonNoMouse button index (1=left, 2=right, 3=middle)
pressedNotrue = press, false = release
positionNoScreen position

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full disclosure burden and delivers little: it does not state whether the game must be running/focused, whether press and release must be issued as a pair, whether the cursor moves as a side effect, or what is returned. The phrase 'in the running game' hints at a runtime precondition but never makes it explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is appropriate for a simple input primitive. It is concise to the point of under-specification, but the structure itself is clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with a nested object, no annotations, and no output schema, the description is too thin: nothing explains default behavior when zero required parameters are supplied, coordinate semantics, or the interaction model between press and release. An agent could invoke it but would be guessing about runtime preconditions and side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (button indices, pressed semantics, and the nested x/y position are all documented in the schema), so the baseline of 3 applies. The description adds no meaning beyond that, such as default click behavior when 'pressed' is omitted or what coordinate space 'position' uses.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('simulate') and resource ('mouse button click') and scopes it to 'the running game', so the action is unambiguous. It does not distinguish this from the adjacent simulate_mouse_move or simulate_action tools, so an agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to prefer this tool over simulate_mouse_move, simulate_action, or simulate_sequence, and no preconditions such as requiring the game window to be focused. The only contextual hint is the phrase 'in the running game', which is incidental rather than deliberate guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools