Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_input_action

Create or update an Input Map action and bind input events, so you can define or change keyboard, mouse, or controller controls for Godot projects.

Instructions

Create or update an input action in the Input Map.

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": "set_input_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction name
eventsNoArray of input event objects to bind

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 bears the full burden and mostly fails it. It never states the critical upsert behavior: whether supplying 'events' replaces the existing bindings or merges with them, what happens to an existing action when only 'action' is passed, or whether the change is persisted immediately or requires a save.

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 efficiently written, though its brevity reflects under-specification rather than disciplined economy of a complete definition.

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 mutation tool with no annotations and no output schema, the definition is too thin. The most consequential question for an upsert with an 'events' array — replace versus append — is left entirely unanswered, and there is no mention of return value or error behavior.

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%, so both 'action' and 'events' are already documented in the schema, setting the baseline at 3. The description adds only the contextual framing that these live in the 'Input Map' and that 'events' are bindings, but contributes no format, ordering, or replacement semantics beyond the schema.

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 pair and resource: 'Create or update an input action in the Input Map.' An agent can immediately tell this mutates input-map configuration rather than reading it. It does not name or differentiate itself from any sibling (e.g. get_input_actions), so it stops short of a 5.

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 use this versus alternatives, no prerequisites, and no statement of which project/context the Input Map belongs to. The only implied usage cue is the 'create or update' upsert phrasing, which hints the tool handles both cases but never confirms it.

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