Skip to main content
Glama

game_get_state

Read-only

Fetch a player's current FiveM state—position, heading, health, armor, vehicle, clock, resolution, and NUI focus—to inspect or debug gameplay.

Instructions

Player position, heading, health, armor, vehicle, clock, resolution and whether NUI has focus

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

Input Schema

NameRequiredDescriptionDefault
playerNo
serverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The field list adds useful disclosure about what the read returns (including NUI focus and vehicle), but nothing about defaults, whether an omitted player/server means the caller's own context, or what happens if the target is absent.

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?

It is a single short fragment with no wasted words, but it is not a sentence and lacks a front-loaded verb, which slightly hurts scannability. Appropriate length for the tool's simplicity.

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?

There is no output schema, so the description carries the burden of describing the return value; it lists field names but not their types or structure, and it omits all parameter meaning. For a low-complexity read tool this is close but leaves the targeting semantics entirely unexplained.

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% and the description says nothing about the two optional parameters (player, server). With both defaulting and no required fields, an agent cannot tell from any source whether omitting them means "my own state" or something else — the description needed to compensate here and does not.

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

Purpose3/5

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

The description is a noun-phrase inventory ("Player position, heading, health, armor, vehicle, clock, resolution and whether NUI has focus") with no verb, so the action (read current game state) must be inferred from the name. It does carve out a distinct scope relative to siblings like performance_get or server_get_status by naming game-specific fields, but it never states the operation explicitly.

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?

There is no guidance on when to call this versus alternatives such as performance_get, game_get_entities, or server_get_status, and no mention of preconditions. The agent must guess that this is the snapshot-of-player-environment tool.

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