Skip to main content
Glama

Remove an object

remove_object
Destructive

Removes for good something placed (a canvas, prop, lamp, fan, cannon, label or door) or a restricted zone, by its id from look. A cannon's price doesn't come back. Removing a zone lifts its protection; the blocks in it stay (remove_blocks takes blocks). To change a thing instead, use edit_object or move_object. Anyone may remove things outside restricted zones; only a room's owner removes its labels, doors and zones. Only adding it again undoes it. 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>"
    },
    "name": "remove_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIts id, as look gives it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give destructiveHint=true and readOnlyHint=false; the description adds substantial context beyond that: irreversibility ('Only adding it again undoes it'), no refund of a cannon's price, that zone removal lifts protection but preserves blocks, and a cost of one edit. These are exactly the consequences an agent needs before committing a destructive call.

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 action and its scope, then the consequences, then the alternatives and permissions — a logical order with no filler sentences. The phrasing is slightly telegraphic ('Removes for good something placed'), which costs a little parseability, but each sentence carries 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 single-parameter destructive tool with no output schema, the definition covers what is destroyed, what is preserved, permissions, irreversibility, and cost. Nothing an agent needs 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.

Parameters3/5

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

Only one parameter and schema coverage is 100%, with the schema already saying 'Its id, as look gives it.' The description's 'by its id from look' restates that provenance rather than adding new meaning, so baseline 3 applies.

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 (removes for good) plus the exact resource set it accepts — canvas, prop, lamp, fan, cannon, label, door, or restricted zone — and identifies the id as the selector. An agent can distinguish this from edit_object, move_object, and remove_blocks without opening any 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?

Explicitly routes to alternatives: edit_object or move_object 'to change a thing instead,' and remove_blocks for the blocks left inside a removed zone. It also states who may invoke it (anyone outside restricted zones; only the room owner for labels, doors, zones), which is the precondition an agent needs before calling.

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.