Skip to main content
Glama

Remont β€” renovation planner

Save floor layout

save_layout

Saves the floor layout of a plan (shown in the plan's 🏠 Layout tab, where the user drags furniture). Coordinates in cm from the top-left inner corner of each floor; x to the right, y down. Per floor: name, W, H (inner size), height_cm (ceiling), rooms [{name, label (area text), x, y, w, h, wet, block (stairs/technical, not a room), finish tiles|spc|none}], walls [{x,y,w,h}] (inner walls as rectangles), doors [{x,y,len,v,hinge,swing,open}] (v: true = in a vertical wall, opening runs down from y; false = horizontal wall, runs right from x; hinge "start" (default, at x,y) or "end"; swing 1 = opens toward +x/+y, -1 = toward -x/-y; open false = shown closed; the user edits these in the widget), windows [{x,y,len,v,label,sill_cm,height_cm}] on the outer edge (x=0 / x=W / y=0 / y=H), fixed [{name,x,y,w,h}] (stairs, shower), furniture [{name,x,y,w,h,height_cm,elev_cm,kind}] β€” furniture and appliances in one list: kind "appliance" for equipment (fridge, washer, dishwasher, oven, hob, hood, boiler, water heater, TV, air conditioner, radiator), height_cm = the item's own height, elev_cm = how high it is mounted above the floor (wall TV β‰ˆ100, boiler β‰ˆ120, hood β‰ˆ150, AC β‰ˆ220, hob on the counter 90); give height_cm for every item. presets [{name, items:[same fields]}] (ready furniture variants). Build it from a drawing or photos of the floor plan; names in the user's language. Merging: floors are matched by position (or index); a floor you send replaces the fields you give, other fields and floors stay β€” so to move furniture send only [{index, furniture}]. replace: true replaces the whole layout. The open plan picks it up within a minute. Returns rooms derived from the layout β€” pass them to recalc_plan if the user wants materials recalculated from the layout.

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>",
      "layout": "<layout>"
    },
    "name": "save_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
layoutYes
replaceNo
view_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations: it discloses the merge semantics (floors matched by position or index, only supplied fields overwritten, other fields and floors preserved), the destructive full-overwrite path via replace:true, the propagation delay ('the open plan picks it up within a minute'), and the return value (derived rooms). These are exactly the behaviors an agent cannot get from readOnlyHint=false / destructiveHint=false.

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?

Almost every clause earns its place given the undocumented nested payload, but it is delivered as one dense run-on block with em-dashes and parenthetical asides, making it hard to scan. The core purpose is front-loaded, yet the field-level reference and the merging rules are buried mid-paragraph rather than set apart.

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

Completeness5/5

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

For a write tool with a 0%-covered nested schema and no output schema, the description supplies everything needed to invoke it correctly: payload shape, coordinate conventions, merge vs. replace semantics, and what comes back. An agent can construct a valid call without guessing.

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?

Schema coverage is 0% and the schema types layout as a bare object, so the description carries the entire burden β€” and does: coordinate origin and axis direction, cm units, per-floor fields, every room/wall/door/window/fixed/furniture/preset sub-field, the meaning of v/hinge/swing/open, the wet/block/finish flags, default hinge value, and practical elev_cm/height_cm reference values. Only view_id is left implicit ('of a plan').

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?

Opens with a specific verb and resource β€” 'Saves the floor layout of a plan' β€” and anchors it to the concrete UI location ('🏠 Layout tab, where the user drags furniture'), so an agent knows exactly what domain object is being written and can separate it from plan/catalog/progress savers among the siblings.

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?

Gives real usage context: build the layout from a drawing or photos, send only [{index, furniture}] to move furniture, use replace:true for a full overwrite, and hand the returned rooms to recalc_plan when materials must be recalculated. It stops short of naming save_layout_furniture or distinguishing this tool from it, which is the one routing gap.

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