Skip to main content
Glama

game_execute_command

Destructive

Runs a client-side FiveM console command as if typed in F8, so resources can trigger commands like opening a UI; the command must be in allowClientCommands.

Instructions

Run a client console command as if typed in F8 (e.g. a resource's RegisterCommand to open its UI). Must be in allowClientCommands. Arguments are single tokens.

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": {
      "command": "<command>"
    },
    "name": "game_execute_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
playerNo
serverNo
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the risk profile is covered. The description adds genuinely new behavior: execution context is the client F8 console and the command must be present in the allowClientCommands allowlist. It stops short of describing failure behavior or what happens when the allowlist check fails.

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?

Three short sentences, front-loaded with the core action, then the example, then the prerequisite and argument constraint. No filler. Phrasing is slightly clipped ('Must be in allowClientCommands'), which costs a bit of clarity.

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?

This is a destructive execution tool with no output schema and zero schema coverage on four parameters. The description covers the command and argument shape but omits the player/server targeting parameters, return behavior, and error semantics, which an agent needs to invoke it safely.

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% across four parameters. The description clarifies that arguments are single tokens, which meaningfully constrains the 'args' array, but the 'player' and 'server' parameters are left entirely unexplained in both schema and prose, leaving an agent to guess at targeting semantics.

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 and resource: 'Run a client console command as if typed in F8'. The word 'client' implicitly distinguishes it from server-side command execution, and the example clarifies the intended effect. It never names the alternative tool outright, so an agent must infer the split from sibling names alone.

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 states one hard prerequisite ('Must be in allowClientCommands') and gives a concrete use case (opening a resource's UI via RegisterCommand). It does not say when to prefer this over server_execute_command or what to do if the command is not allowlisted, so usage is only partially guided.

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