Skip to main content
Glama

Get room layout

get_room_layout
Read-only

The CONFIGURATION at a moment: where every unit of equipment stands — put there by the last occurrence whose layout matters that had begun by then ('since'), or where it stands of itself — with its point in millimetres and its room. With 'room', only the units in that room. Any member may read.

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": {
      "project": "<project>"
    },
    "name": "get_room_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoThe moment, ISO 8601. Default: now.
roomNoA room's resource id, to see only what stands in it.
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds meaningful behavioral context: how positions are derived from the last relevant occurrence begun by the requested time, what 'since' means, and that any member may read. It still omits return shape/pagination details, but no output schema exists and it covers the core computation.

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

Conciseness3/5

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

Single dense sentence with nested em-dash clauses; the core concept is front-loaded but phrasing like 'last occurrence whose layout matters that had begun by then' is harder to parse than necessary. It avoids filler but sacrifices clarity.

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 read-only layout query with a fully described input schema and no output schema, the definition covers the key concept, time semantics, room filter, permission, and return elements. It could be clearer on exact return structure, but it is largely complete.

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 adds temporal meaning to 'at' (last relevant occurrence begun by then) and clarifies that 'room' restricts to units in that room, beyond the schema's terse descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource, the layout configuration at a moment, and what it returns: every equipment unit with its millimetre point and room. The opening is recognizable despite awkward domain phrasing, but it does not explicitly contrast with get_layout_settings.

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

Usage Guidelines3/5

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

Implied usage only: retrieve layout at a moment, optionally filtered to one room; no explicit when-to-use or when-not-to-use guidance relative to siblings such as get_layout_settings. The permission note 'Any member may read' helps access but not tool selection.

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