Skip to main content
Glama
Sign In

ThingsPool

by net.thingspool
OverviewDiscussionsAdmin

Move an object

move_object

Moves something placed (a canvas, prop, lamp or fan, 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. 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. Changed1 schema field changed
    • addedInput schema / properties / top / description
      Added value: +"On a floor or ceiling, the way a picture's top points: north (the default), south, east or west. Ignored on a wall."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description adds real behavioral context beyond that: size is preserved and the object is centered on the side as far as it fits, labels/doors are wall-only, zones are immovable, and the call costs one edit against a budget.

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?

Every clause carries information: the move semantics come first, alternatives second, failure modes last. The opening sentence is very long and semicolon-chained, which costs some readability, but there is no filler to cut.

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 mutation tool with no output schema, three parameters at full schema coverage and only safety annotations, the description covers what the move does, what is rejected and why, what it costs, and which siblings to use instead. Nothing an agent needs before invoking it 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. The description still adds meaning the schema does not: which sides are legal for which object types (labels and doors only on walls), that a full or hidden side is rejected, and that 'on' means a side of another block. It does not discuss 'top' beyond schema.

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 (moves) and enumerates the exact resources it applies to (canvas, prop, lamp, fan, label, door), plus the target (another block's side). It explicitly names the sibling tools edit_object and add_object and how this differs, so an agent can separate move from edit or create without opening a schema.

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 explicit routing: use edit_object to change content, add_object to create, remove_object plus add to relocate a zone (zones can't move). It also names refusal conditions (unknown id, hidden or full side, restricted zone, spent edits), which tells the agent when this call will fail.

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

All ThingsPool toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources