Skip to main content
Glama

placeable-list

Read-onlyIdempotent

List one kind of object on a scene with ids and positions (scene pixels): wall, note, light, sound (ambient sound), tile, drawing, region. For a region id: its behaviors with config, or tokens: true for the tokens inside it, or point to test whether a spot is inside. kind door-sound lists the door sounds a wall can use. scene-get gives a summary of everything at once. 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>"
    },
    "name": "placeable-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoRegion ID (kind region) — details with behaviors
kindYes
pointNoWith a region id: is this point (pixels) inside?
tokensNoWith a region id: tokens inside it
sceneIdNoScene ID (from scene-list); default: the viewed scene

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds the return shape (ids and positions in scene pixels), the conditional behavior when id is supplied, and a hard dependency ("Requires bridge module 8.19.0+") that is not in any structured field. It does not mention pagination or limits, which is the only notable omission for a list tool.

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?

It is front-loaded with the core action and kinds, then layers the conditional modes and the dependency note; nearly every clause earns its place. The telegraphic style ("or tokens: true for the tokens inside it") is dense but still parseable, slightly at the cost of readability.

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?

With no output schema, the description carries return-shape duty and does describe ids/positions in pixels and the richer region payloads. Combined with a 5-parameter nested schema, a version requirement, and a named alternative, it is nearly complete; only list size/pagination behavior is unaddressed.

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 80%, so the baseline is 3, and the description adds genuine meaning on top: it explains that id triggers region behavior/config output, that tokens: true narrows to tokens inside the region, and that point tests containment. These are cross-parameter conditional semantics the per-field schema descriptions only state piecemeal.

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 description opens with a specific verb+resource ("List one kind of object on a scene"), enumerates the valid object kinds, and states what is returned (ids and positions in scene pixels). It also distinguishes itself from scene-get, which "gives a summary of everything at once," so an agent can pick between them without opening either 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?

It gives clear routing context: use this for one object kind with detail, use scene-get for a full summary, and it explains the region-id sub-modes (behaviors with config, tokens: true, point test) plus the special door-sound kind. It stops short of explicit when-not-to-use guidance or stating prerequisites for the region modes beyond the required id.

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