dos2-gm-mcp

Overview Schema Source Related Servers Discussions Admin

Teleport a live character

dos2_live_move

Idempotent

Teleports a player character or NPC in the running Divinity: Original Sin 2 game to x,y,z coordinates or beside another character with a configurable offset, without editing campaign files.

Instructions

Teleports one character on the live level to the point x, y, z, or next to another character with the offset dx, dz. Works on NPCs and on player characters.

Changes only the running game, not the campaign files. During the Game Master pause the move is applied after
unpausing (the result has applies_on_unpause=true). Fails with an error when who matches no character or more
than one (then pass a GUID), or when neither a full x, y, z nor near is given. Needs the bridge (see
dos2_live_status). Get positions from dos2_live_characters.

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": {
      "who": "<who>"
    },
    "name": "dos2_live_move"
  }
}

Input Schema

Name	Required	Description
`x`	No	World X coordinate in metres. Give all of x, y, z, or use near instead.
`y`	No	World Y (height) coordinate in metres. Give all of x, y, z, or use near instead.
`z`	No	World Z coordinate in metres. Give all of x, y, z, or use near instead.
`dx`	No	Offset in metres along X from the near character (default 1.5). Ignored without near.
`dz`	No	Offset in metres along Z from the near character (default 0). Ignored without near.
`who`	Yes	The character to act on: its GUID, its exact name, or a unique part of its name (see dos2_live_characters).
`near`	No	Place relative to this character (GUID or name) instead of giving x, y, z.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.1Nov 11, 2026

addedInput schema / properties / dx / description

Added value: +"Offset in metres along X from the near character (default 1.5). Ignored without near."

addedInput schema / properties / dz / description

Added value: +"Offset in metres along Z from the near character (default 0). Ignored without near."

addedInput schema / properties / near / description

Added value: +"Place relative to this character (GUID or name) instead of giving x, y, z."

addedInput schema / properties / who / description

Added value: +"The character to act on: its GUID, its exact name, or a unique part of its name (see dos2_live_characters)."

addedInput schema / properties / x / description

Added value: +"World X coordinate in metres. Give all of x, y, z, or use near instead."

addedInput schema / properties / y / description

Added value: +"World Y (height) coordinate in metres. Give all of x, y, z, or use near instead."

addedInput schema / properties / z / description

Added value: +"World Z coordinate in metres. Give all of x, y, z, or use near instead."

First observedv0.1.0Nov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the annotations it discloses that the change is runtime-only and does not touch campaign files, and that during the Game Master pause the move is deferred until unpause with applies_on_unpause=true in the result. That deferred-execution behavior is non-obvious and valuable; the only minor gap is no note on what happens if the target is dead/out of bounds.

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?

Front-loaded with the core action and the two targeting modes, followed by scope, runtime semantics, and error conditions in a logical order. Slightly dense over four lines but every clause carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter mutation tool with no output schema, the description covers preconditions, targeting rules, failure modes, persistence scope, and even the one result field an agent might check (applies_on_unpause). Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: 'who' accepts a GUID, exact name, or unique name fragment, and ambiguity is an error requiring a GUID. It also clarifies the all-or-nothing relationship among x, y, z and the near-with-offset alternative, which the schema only implies per-parameter.

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

Purpose5/5

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

States a specific verb and resource ('Teleports one character on the live level') and enumerates both targeting modes (absolute x, y, z vs. relative to a 'near' character with dx, dz). It also names the scope boundary ('live level', 'NPCs and player characters'), which separates it from the campaign-file siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete prerequisites (needs the bridge, see dos2_live_status) and routes the agent to dos2_live_characters for obtaining positions and GUIDs. It also states the two failure conditions (ambiguous/non-matching 'who', and missing coordinates), which is exactly the when-it-won't-work guidance an agent needs.

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