Skip to main content
Glama

get_input_map

Retrieve input action mappings for Godot projects to configure keyboard, controller, and device controls for gameplay interactions.

Instructions

Get the project input action mappings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'get_input_map' tool, which extracts input action mappings from the project info.
    handler: async (_ctx) => {
      const info = getProjectInfo();
      if (!info) {
        return makeTextResponse({
          error: "No Godot project detected",
          data: null,
        });
      }
    
      return makeTextResponse({
        data: info.inputActions.map((a) => ({
          name: a.name,
          deadzone: a.deadzone,
          events: a.events.map((e) => {
            const filtered: Record<string, unknown> = { type: e.type };
            if (e.properties.key_name) filtered.key_name = e.properties.key_name;
            if (e.properties.physical_keycode)
              filtered.physical_keycode = e.properties.physical_keycode;
            if (e.properties.button_index) filtered.button_index = e.properties.button_index;
            if (e.properties.joypad_axis != null) filtered.joypad_axis = e.properties.joypad_axis;
            if (e.properties.axis_value != null) filtered.axis_value = e.properties.axis_value;
            for (const mod of ["ctrl_pressed", "shift_pressed", "alt_pressed", "meta_pressed"]) {
              if (e.properties[mod] === true) filtered[mod] = true;
            }
            return filtered;
          }),
        })),
        metadata: { source: "index" },
      });
    },
  • Registration of the 'get_input_map' tool within the project tools definition.
    {
      name: "get_input_map",
      description: "Get the project input action mappings.",
      schema: {},
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does ('Get'), but doesn't describe what the output looks like, whether it's a read-only operation, if there are any side effects, or how the data is structured. This leaves significant gaps for an agent to understand the tool's behavior.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized for a tool with no parameters and gets straight to the point.

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?

Given the complexity of retrieving project mappings and the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'input action mappings' are, what format they're returned in, or how this tool differs from other data retrieval tools in the sibling set. More context is needed for an agent to use this effectively.

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 has 0 parameters with 100% schema description coverage, so the schema fully documents the input requirements. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters, earning a baseline score of 4 for not introducing confusion.

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 clearly states the action ('Get') and the resource ('project input action mappings'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_config', 'get_project_settings', or 'get_runtime_state' that also retrieve project-related data, leaving some ambiguity about what specifically distinguishes this tool.

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 description provides no guidance on when to use this tool versus alternatives. With many sibling tools that retrieve project information (e.g., 'get_config', 'get_project_settings'), there's no indication of what makes 'input action mappings' unique or when this specific data is needed.

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/woohq/godette-mcp'

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