Skip to main content
Glama

game_spawn

Destructive

Spawn a client-local test vehicle, ped, or object for FiveM development, optionally warp the player into the spawned vehicle, and clean it up with test_cleanup.

Instructions

Spawn a client-local test vehicle, ped or object (cleaned up by test_cleanup). warpIn puts the player in a spawned vehicle.

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": {
      "kind": "<kind>",
      "model": "<model>"
    },
    "name": "game_spawn"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
modelYes
playerNo
serverNo
warpInNo
headingNo
positionNo

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 openWorldHint=false, so the safety profile is partly covered. The description adds genuinely useful context that annotations cannot convey: spawns are client-local test artifacts and are reclaimed by test_cleanup. It does not explain why the operation is destructive, whether spawns persist across sessions, or what happens if the model name is invalid.

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?

Two short sentences, front-loaded with the action and its scope, with the cleanup relationship and the warpIn flag appended. Nothing is wasted, though the parenthetical cleanup note is slightly awkwardly embedded.

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?

For a destructive 7-parameter mutation with a nested position object and no output schema, the definition covers the core action and the cleanup lifecycle but omits the return value (does it yield an entity handle needed for game_delete_entity?) and leaves most parameters undocumented. Adequate as a minimum, but with clear gaps.

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 7 parameters, so the description must carry the load, yet it only explains warpIn. The required kind and model parameters, plus player, server, heading and the nested position object, receive no meaning beyond their names — for example, whether server targets a specific server session or how heading interacts with position.

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?

States a specific verb (Spawn) plus the resource and its three valid kinds (vehicle, ped, object), and qualifies it as client-local and test-only. That distinguishes it reasonably from siblings like game_get_entities, though it does not explicitly contrast with game_execute_command or other mutation paths.

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 word 'test' and the reference to test_cleanup imply this belongs in a test workflow, and warpIn's effect is described. However, there is no explicit when-to-use vs when-not guidance, no statement about prerequisites (is a running game session required?), and no indication of when to prefer game_execute_command instead.

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