Skip to main content
Glama

Move an object

move_object

Moves something placed (a canvas, prop, lamp, fan or cannon, or in your own room a label or door) onto another block's side, keeping its size, as near the side's middle as it fits; labels and doors go only on walls, and a cannon on a floor or a wall. Use edit_object to change what it shows, add_object for a new one. A zone can't move: remove it and add another. Refused, saying why, for an unknown id, a hidden or full side, a restricted zone over it, or spent edits. Costs one edit.

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": {
      "id": "<id>",
      "on": "<on>"
    },
    "name": "move_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIts id, as look gives it
onYesThe block's side it hangs on
topNoOn a floor or ceiling, the way a picture's top points: north (the default), south, east or west. Ignored on a wall.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond readOnlyHint=false, the description discloses cost ('Costs one edit'), the full refusal set (unknown id, hidden or full side, restricted zone over it, spent edits) and the placement rule ('as near the side's middle as it fits'). It also states type-vs-surface constraints (labels and doors only on walls; cannon on floor or wall). Lacking only detail on what happens to the prior position or any partial-failure behavior.

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?

The action and its constraints are front-loaded, and the alternatives and refusal conditions follow in a logical order with no filler. It is dense and semicolon-heavy, but each clause carries distinct information.

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 mutating tool with a nested target object and no output schema, the definition covers what moves, where it lands, what is rejected and why, and the cost. An agent has enough to call it correctly and to predict failure modes without further discovery.

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 about how 'on' resolves: the object is snapped near the side's middle and keeps its size, and surface compatibility constrains which side values are legal. It adds little for 'top', which the schema already covers.

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?

It gives a specific verb (moves) and resource (a placed canvas, prop, lamp, fan, cannon, label or door) and states the destination model explicitly ('onto another block's side, keeping its size'). The enumeration of movable object types and the note that zones cannot move make it clearly distinguishable from add_object, edit_object and remove_object.

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?

Alternatives are named with the condition that selects them: 'Use edit_object to change what it shows, add_object for a new one.' It also tells the agent what to do instead for zones ('remove it and add another'), which is a when-not clause with a redirect rather than a bare refusal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.