Skip to main content
Glama

Remont — renovation planner

Read floor layout

get_layout
Read-only

Returns the floor layout of a plan (floors, rooms, walls, doors, windows, furniture in cm), the rooms derived from it (area, length × width, wet, level) for recalc_plan, and corners: the corner letters shown on the plan (room i has letters 4i..4i+3 clockwise from top-left: A B C D, E F G H…) with coordinates and side lengths, so «wall A-B of the kitchen» means the same to you and the user.

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": {
      "view_id": "<view_id>"
    },
    "name": "get_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
view_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish this as a safe, closed-world read (readOnlyHint=true, openWorldHint=false). The description adds real value by spelling out the returned content and units (cm) in the absence of an output schema, but says nothing about failure modes (e.g. missing or empty plan) or size of the response.

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 a single front-loaded sentence whose parenthetical inventory is dense but each clause carries information (contents, units, derived fields, letter indexing scheme). The nesting is heavy but nothing is filler.

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 the full burden of describing return values, and it does so thoroughly, including the corner-letter ordering rule needed to interpret the data. The one unresolved item is what a view_id is relative to a plan.

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?

There is a single required parameter, view_id, with 0% schema description coverage, so the description is the only place meaning could be added. It refers to 'a plan' rather than a view, leaving the relationship between a view_id and a plan unexplained; the baseline of 3 applies for a one-parameter tool but the gap is real.

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?

The description opens with a specific verb and resource ('Returns the floor layout of a plan') and enumerates the payload precisely: floors, rooms, walls, doors, windows, furniture, derived room metrics, and corner letters with coordinates. It does not explicitly contrast itself with sibling readers such as get_plan, so it stops short of a 5.

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?

Usage is implied rather than stated: the layout data is 'for recalc_plan', and the corner-letter convention is framed for communicating with the user. There is no explicit 'call this before recalc_plan' or 'use save_layout to modify' style routing, so an agent must infer the workflow position.

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