Skip to main content
Glama

game_teleport

Destructive

Moves a player on foot to specified world coordinates in a FiveM server, enabling precise repositioning for testing or scenario setup.

Instructions

Teleport the player (on foot) to world coordinates

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": {
      "position": "<position>"
    },
    "name": "game_teleport"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerNo
serverNo
positionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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 supplied structurally. The description adds the 'on foot' applicability constraint, but says nothing about why a teleport is destructive, whether it cancels current actions or vehicle state, what happens on out-of-range or blocked coordinates, or which server/player it defaults to. Useful but thin given it is a state-mutating world operation.

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?

A single nine-word sentence with the action and scope front-loaded and no filler. It is efficient, though the brevity means nothing beyond the minimum is communicated.

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?

For a destructive mutation tool with three parameters at 0% schema coverage, a nested position object with coordinate bounds, and no output schema, the description is far too sparse. It does not cover the player/server targeting parameters or coordinate semantics, leaving the agent to guess at correct invocation.

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 carry parameter meaning and largely does not. It only gestures at 'world coordinates' for the nested x/y/z position; the 'player' identifier (1-65534) and the 'server' selector are entirely unexplained, including what happens when they are omitted.

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 and target: 'Teleport the player ... to world coordinates', with a scope restriction ('on foot') that distinguishes it from vehicle/entity operations like game_spawn. It stops short of naming any sibling or explaining how it differs from game_execute_command or game_input, so an agent still has to infer routing.

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 when-to-use or when-not guidance, no prerequisites, and no mention of alternatives (e.g. game_spawn for creating entities). The only constraint offered, '(on foot)', reads as a behavioral scope note rather than invocation guidance.

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