Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

simulate_action

Trigger Godot Input actions to automate gameplay testing and enable AI agents to control game projects remotely.

Instructions

Simulate Godot Input action. (Compatibility tool)

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_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden but omits critical behavioral details: what 'autoConnect' connects to, what happens when 'timeoutMs' is reached, whether the simulation triggers actual game logic, and what 'additionalProperties: true' implies for action parameters.

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?

The description is efficiently worded (4 words plus parenthetical) and front-loaded with the verb, but it is inappropriately terse given the complete absence of schema documentation and annotations. The '(Compatibility tool)' note is valuable but underdeveloped.

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?

With zero schema descriptions, no annotations, and no output schema, this simulation tool requires substantial descriptive compensation. The description fails to explain the return behavior, error states, or the significance of 'additionalProperties: true' for specifying which action to simulate.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description fails to document either 'timeoutMs' or 'autoConnect'. While 'Input action' implies the additionalProperties likely contain the action name/data, the description provides no syntax guidance or examples for these undocumented parameters.

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

Purpose3/5

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

The description states the basic function (simulating Godot Input actions) but fails to distinguish this tool from siblings like 'simulate_key' or 'simulate_sequence'. It doesn't clarify that this targets Godot's mapped Input actions versus raw hardware input, leaving ambiguity for agent selection.

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?

The '(Compatibility tool)' parenthetical hints this may not be the preferred approach, but provides no explicit guidance on when to use alternatives like 'simulate_key' or what has replaced this tool. No prerequisites or exclusion criteria are mentioned.

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