Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

simulate_sequence

Simulate ordered input events in the running game to test controls and gameplay behavior.

Instructions

Simulate a sequence of input events 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": {
      "events": "<events>"
    },
    "name": "simulate_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsYesArray of input event objects to simulate in order

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 exist, so the description carries the full burden, and it discloses little beyond the 'running game' prerequisite. It never says whether events fire in real time or instantly, what happens on an invalid event, whether the call blocks, or what is returned — important for a tool that mutates live game state.

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. It is efficient, though its brevity is also the source of the missing behavioral detail.

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 that injects input into a live game with zero annotation coverage and no output schema, the definition omits prerequisites, event-object format, timing semantics, and failure behavior. An agent cannot safely construct the events array from this description alone.

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?

The schema's items are a bare object with no defined properties, so the shape of each event object (key codes, coordinates, event types, timing) is documented nowhere. The description only restates 'input events' and does not compensate for that gap.

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+resource: 'Simulate a sequence of input events in the running game.' The word 'sequence' implicitly separates it from single-input siblings like simulate_key or simulate_mouse_click, but no sibling is named, so differentiation is left to inference.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not guidance and no named alternative. Only implied usage: use this when you need multiple input events rather than one, which an agent must infer from the word '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