Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_input_actions

Retrieve all input actions and their event bindings from the project Input Map to inspect or audit controls.

Instructions

Get all input actions and their event bindings from the project Input Map.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/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 discloses that the read is scoped to the project Input Map and covers all actions plus their event bindings, which tells the agent this is a whole-map read rather than a filtered query. It does not say whether built-in engine actions are included, what the binding representation looks like, or how large the result may be.

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?

A single sentence with zero wasted wording, and the scope ('from the project Input Map') is front-loaded alongside the resource. Nothing is buried or repeated.

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?

With no annotations and no output schema, the description is the only source of information about the response, and it only sketches it as 'input actions and their event bindings.' That is enough to know the shape at a high level but leaves the actual binding structure and inclusion of default actions unspecified. For a simple zero-param getter this is adequate, not thorough.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description correctly implies no filtering or selection is possible and that the entire Input Map is returned, which is consistent with the empty input 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 states a specific verb and resource: 'Get all input actions and their event bindings from the project Input Map.' It is unmistakably a read of the project's input map, which contrasts implicitly with the mutating sibling set_input_action. It stops short of naming that sibling explicitly, so a 4 rather than 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 Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use statement, and no alternative is named. Usage is only implied: an agent would infer it should call this when it needs to inspect existing input bindings before rebinding or generating input code. That inference is reasonable but not stated.

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