Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

simulate_key

Send keyboard key press or release events to a running Godot game with optional Ctrl, Alt, and Shift modifiers to test controls and gameplay interactions.

Instructions

Simulate a keyboard key event 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": {
      "keycode": "<keycode>"
    },
    "name": "simulate_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
altNoHold Alt modifier
ctrlNoHold Ctrl modifier
shiftNoHold Shift modifier
keycodeYesKey constant name (e.g. KEY_SPACE)
pressedNotrue = press, false = release (default: true)

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. It does not say whether the event is delivered to the focused window or a specific target, whether it is fire-and-forget or returns an acknowledgement, what happens on an invalid key constant, or whether key state persists across calls (relevant given the 'pressed' flag can leave a key logically held down).

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 or redundancy. It is efficient, though its brevity is partly what leaves the behavioral gaps noted elsewhere.

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 tool with five parameters, no annotations, and no output schema, the description is too thin. An agent cannot tell whether the call requires an active game session, whether modifiers must be released explicitly, or what a failure looks like, all of which matter for correct invocation.

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%, and the schema already documents each modifier flag, the keycode format with an example, and the press/release default. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb ('Simulate') and resource ('a keyboard key event') with a scope qualifier ('in the running game'), which is enough to distinguish it from simulate_mouse_click or simulate_mouse_move. It stops short of explicitly differentiating itself from simulate_action or simulate_sequence, which also sound input-driven.

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 choose this over simulate_action, simulate_sequence, or the mouse siblings, and no explicit prerequisite statement beyond the passing phrase 'in the running game'. The agent must infer that the game must be running and focused before calling.

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