Skip to main content
Glama

move_objects

Shift selected map objects by dx and dy pixels. Symbols and labels move their positions, while paths and territories move every point.

Instructions

Shift objects by (dx, dy) map pixels. Symbols/labels move their position; paths and territories move every point.

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": {
      "ids": "<ids>",
      "dx": "<dx>",
      "dy": "<dy>"
    },
    "name": "move_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxYes
dyYes
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that paths and territories translate every vertex while symbols/labels shift their anchor, but says nothing about mutating the map, persistence/undo, or what happens to invalid or missing ids.

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 tight sentences with the core operation and its units front-loaded, and the object-type caveat second. No filler or repetition.

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?

A mutation tool with no annotations, no output schema, and fully undocumented parameters needs more: id format, whether the change is persisted or undoable, and error behavior are all absent. The offset and per-type geometry behavior are, however, adequately covered.

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

Parameters3/5

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

Schema coverage is 0%, and the description adds real meaning for dx/dy by specifying map-pixel offsets rather than abstract units. The required 'ids' parameter is left unexplained — which object types are accepted and in what format is not stated.

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 (shift) and resource (objects) plus the offset semantics in map pixels, and distinguishes behavior by object type (symbols/labels vs paths/territories). It stops short of differentiating itself from geometry-changing siblings such as update_object or raise_area.

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?

Usage is only implied: it moves existing objects by a relative offset, which contrasts implicitly with absolute-editing tools. There is no explicit when-to-use, when-not-to-use, or named alternative.

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