Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

simulate_mouse_move

Moves the mouse cursor to a specified screen position in the running Godot game, enabling AI-driven testing and interaction with game UI or gameplay elements.

Instructions

Simulate mouse movement in the running game.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "position": "<position>"
    },
    "name": "simulate_mouse_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionYesTarget screen position

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden and mostly fails it. It does not say whether the move is instantaneous or interpolated, whether it blocks, whether it requires the game window to be focused, or what happens if the cursor is already at the target. Only the phrase "in the running game" adds a precondition beyond the schema.

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

Conciseness3/5

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

A single short sentence with no wasted words, which is good structurally. However, its brevity reflects under-specification rather than disciplined concision, leaving key invocation details unstated.

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 one-parameter simulation tool with no annotations and no output schema, the description should at least cover coordinate semantics, timing behavior, and success/failure signaling. None of those are addressed, so an agent cannot predict the effect of calling it beyond moving the pointer somewhere.

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 coverage is 100% and the nested position object is already documented as "Target screen position" with required x and y. The description adds no coordinate-space clarification (screen vs window vs game-world) or value ranges, so it neither compensates nor detracts.

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 gives a specific verb+resource ("Simulate mouse movement") scoped to "the running game", which separates it from file/node tools and from the click sibling. It does not explicitly contrast with simulate_mouse_click or simulate_action, so the differentiation is implied rather than stated.

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 when-to-use guidance: no statement of when to pick this over simulate_mouse_click, simulate_action, or simulate_sequence, and no prerequisites such as the game being focused or a coordinate origin. The reader must infer all routing from the tool name.

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