Skip to main content
Glama

input_map

Destructive

Manage input actions by listing, adding, removing actions, and binding key, mouse, or joypad events to actions in Godot projects.

Instructions

Input action management.

Actions (required params -> optional):

  • list (-> project_path): all input actions

  • add_action (action_name -> deadzone=0.5, project_path)

  • remove_action (action_name -> project_path)

  • add_event (action_name, event_type, event_value -> project_path)

event_type: key | mouse | joypad. event_value: e.g., KEY_SPACE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
project_pathNoPath to Godot project directory
action_nameNoInput action name
deadzoneNoDeadzone value (for add_action, default: 0.5)
event_typeNoEvent type: key, mouse, joypad (for add_event)
event_valueNoEvent value, e.g., KEY_SPACE (for add_event)

Implementation Reference

  • Security utility listing 'input_map' as a tool that returns external content from project files, used to wrap responses with safety warnings.
    const EXTERNAL_CONTENT_TOOLS = new Set([
      'scripts',
      'shader',
      'scenes',
      'resources',
      'project',
      'nodes',
      'input_map',
      'signals',
      'animation',
      'tilemap',
      'physics',
      'audio',
      'navigation',
      'ui',
    ])
Behavior3/5

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

Annotations indicate destructiveHint=true, so the description's mention of 'add', 'remove' aligns. However, no additional behavioral context (e.g., side effects, permissions, reversibility) is provided beyond the action list.

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 uses a custom notation ('->') and bullet-like structure, but it is somewhat dense and could be more readable. It is mostly concise but not optimally structured for quick scanning.

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?

Given the multi-action nature and no output schema, the description covers the main operations but lacks details on return values, error handling, or context like project_path significance. It is minimally complete.

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?

Schema coverage is 100%, baseline 3. The description adds value by grouping parameters per action, indicating optionality with '->' notation, and explaining event_type and event_value with examples, which goes beyond the schema descriptions.

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

Purpose5/5

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

The description clearly states 'Input action management' and enumerates all sub-actions (list, add_action, remove_action, add_event) with their specific parameter requirements. It distinguishes this tool from siblings by focusing on input actions.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It implicitly covers input action management but lacks when-not-to-use or comparison to sibling tools like animation or audio.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/n24q02m/better-godot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server