Skip to main content
Glama

placeable-delete

Destructive

Delete one scene object by kind and id (from placeable-list): wall, note, light, sound, tile, drawing, region, or a region behavior (with regionId). Cannot be undone. Requires bridge module 8.19.0+.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "placeable-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesObject ID (from placeable-list)
kindYes
sceneIdNoScene ID (from scene-list); default: the viewed scene
regionIdNoRegion ID, for kind behavior

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely new context on top of that: the deletion is irreversible and the tool requires bridge module 8.19.0+, which an agent cannot learn from the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short clauses with zero filler: the action and its scope come first, then the irreversibility warning, then the dependency. Nothing is padded or repeated.

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

Completeness4/5

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

For a destructive, four-parameter tool this covers the essentials an agent needs before calling it: ID provenance, the region-behavior exception, irreversibility, and a version gate. Only error/failure behavior is left unstated, which is minor given there is no output schema to explain.

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 75% and the schema already documents id, sceneId, and regionId. The description's enumeration of kinds duplicates the enum, and its only real semantic addition is clarifying that region behaviors are addressed via kind=behavior plus regionId; the rest is restatement.

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 (delete one scene object by kind and id) and enumerates the supported kinds, so it is clearly distinct from sibling delete tools targeting actors, chat, folders, or scenes. It also names placeable-list as the ID source and carves out the region-behavior case.

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

Usage Guidelines4/5

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

Tells the agent where to get the required ids (placeable-list) and states a hard prerequisite: bridge module 8.19.0+. It does not explicitly say when to prefer a different delete sibling, but the 'scene object' scoping makes the boundary implicit and unambiguous.

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.

Resources