Skip to main content
Glama

game_input

Destructive

Hold FiveM game controls for a specified duration to accelerate, steer, interact, or press keys, using named controls or raw GTA control IDs.

Instructions

Hold game controls for a duration (max 4000 ms), e.g. accelerate to drive or interact to press E. Use a named control or a raw GTA control ID; steer uses value -1 (left) to 1 (right).

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": {
      "controls": "<controls>"
    },
    "name": "game_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerNo
serverNo
controlsYes
durationMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, indicating a mutating operation. The description adds the duration cap (max 4000 ms) and the steer value range (-1 to 1), which are behavioral details. However, it doesn't explain what gets destroyed or the side effects of holding controls, so it adds only moderate value beyond annotations.

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?

The description is a single, front-loaded sentence with examples and constraints, no wasted words. The parenthetical max duration and steer range are efficient, though the sentence is dense and could be slightly clearer with separation.

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 4 parameters with 0% schema coverage, no output schema, and destructive annotations, the description should explain more about the controls array, player/server context, and duration default. It covers the core mechanics but leaves enough undocumented that an agent could mis-invoke.

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?

Schema description coverage is 0%, so the description must compensate. It explains that a named control or raw GTA control ID can be used and that steer uses -1 to 1, which maps to the value parameter. But it doesn't explain player, server, durationMs default/meaning, or the controls array structure, leaving significant gaps.

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 action (holiding game controls for a duration) and resource (game controls), with concrete examples like accelerating to drive or interacting to press E. It distinguishes from siblings like game_execute_command by being about holding controls rather than executing commands, though it doesn't explicitly name alternatives.

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?

It gives examples of what the tool does (accelerate to drive, interact to press E) which implies usage, but doesn't explicitly state when to use this versus game_execute_command or other input-related tools. The max duration of 4000 ms is a useful constraint but not a selection guideline.

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