Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

simulate_action

Triggers or releases an Input Map action in the running Godot game to test input-driven behavior without manual play.

Instructions

Simulate an Input Map action 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": {
      "action": "<action>"
    },
    "name": "simulate_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction name from the Input Map
pressedNotrue = press, false = release (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 behavioral burden. It states the tool simulates an Input Map action in the running game, but does not disclose whether it has side effects, whether it requires game focus, how errors are handled, or what the caller should expect after invocation.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no filler or redundancy. It is appropriately sized for a simple two-parameter simulation tool, though its brevity leaves other dimensions underdeveloped.

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

Completeness3/5

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

For a low-complexity tool with two parameters, full schema coverage, and no output schema, the description covers the basic purpose and running-game context. However, because no annotations are present, it should add more about prerequisites and sibling-tool choice to be fully complete.

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 schema already documents both parameters, including the pressed default. The description only echoes the 'Input Map action' concept and adds no extra detail about action name format, valid values, or pressed/release behavior.

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 and resource: 'Simulate an Input Map action' and adds the execution context 'in the running game.' It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as set_input_action or simulate_key.

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 explicit when-to-use, when-not-to-use, or alternative guidance. The running-game context implies simulation, but an agent cannot tell from the description whether to choose this over set_input_action, simulate_key, or simulate_sequence.

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