Skip to main content
Glama

placeable-set

Create (no id) or update (id) one scene object; data holds its fields — on update only the ones to change. x, y in scene pixels, top-left; radii in scene distance units (feet); paths from file-list. Creating needs: wall c [x1,y1,x2,y2]; note x, y; light x, y; sound x, y, radius, path; tile x, y, width, height, texture.src; drawing x, y, shape; region name; behavior regionId, type. Fields — wall: door none|door|secret, doorState closed|open|locked, move/sense/sound/light none|normal|limited, dir, doorSound. note: entryId (journal), pageId, text, iconSrc, iconSize, textAnchor, global. light: dim, bright, angle, color "#rrggbb", alpha, coloration, luminosity, animation {type, speed, intensity}, darkness {min, max}, walls, vision, hidden. sound: volume 0-1, repeat, walls, easing, hidden, darkness. tile: texture {src, tint, scaleX, scaleY, fit}, rotation, alpha, elevation, hidden, occlusion {modes, alpha}. drawing: shape {type rectangle|ellipse, width, height} or {type polygon, points [x,y,…]}, fill {type none|solid, color, alpha}, stroke {width, color}, text {content, fontSize, color}, hidden. region: shapes [{type rectangle, x, y, width, height} | {type circle, x, y, radius} | {type polygon, points [{x,y}]}], color, elevation {bottom, top}, visibility, hidden. behavior: type (adjustDarknessLevel, displayScrollingText, executeMacro, pauseGame, teleportToken, toggleBehavior, …), name, disabled, config. Requires bridge module 8.19.0+. EXAMPLE: {"kind":"light","data":{"x":1200,"y":800,"dim":30,"bright":15,"color":"#ff9900","animation":{"type":"torch"}}}

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>",
      "data": "<data>"
    },
    "name": "placeable-set"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoObject ID (from placeable-list) to update; omit to create
dataYesThe object's fields (see description)
kindYes
sceneIdNoScene ID (from scene-list); default: the viewed scene
regionIdNoRegion ID (from placeable-list), for kind behavior

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already establish that this is a mutating, non-idempotent, non-destructive write tool. The description adds meaningful behavioral context beyond them: partial updates change only supplied fields, each kind has required fields, and bridge module 8.19.0+ is required. It does not describe return values or error 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 description is long but front-loaded with the create/update rule and coordinate units, and the field lists are necessary for a tool with eight object kinds. The semicolon-separated packing makes it dense to read, though the example and bridge-version note earn their place.

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 complex nested-object mutation tool, the definition covers the essential call semantics, required fields, units, path source, and bridge requirement. It stops short of explaining response shape or error behavior, and it relies on the schema for sceneId and regionId descriptions.

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

Parameters5/5

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

Despite 80% schema description coverage, the description adds substantial meaning: id omission creates while id presence updates, x/y are scene pixels top-left, radii are in feet, and paths must come from file-list. It also enumerates required fields per kind and many optional field semantics that the schema does not capture.

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?

The opening states a specific verb and resource: create without an id, update with an id, exactly one scene object. It also names the object kinds, so an agent can distinguish this from placeable-list and placeable-delete without opening the schema.

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?

The create-versus-update rule is explicit: omit id to create, include id to update. It also notes that sceneId defaults to the viewed scene, regionId applies to behavior, and paths come from file-list; it does not name sibling alternatives such as placeable-delete or placeable-list explicitly.

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