Skip to main content
Glama

Remont — renovation planner

Recalculate plan

recalc_plan

Sets or changes the rooms of an already shown plan — names, area_m2 or length_m × width_m, floor type, bathroom (wet), level, ceiling height — stores them with the plan and recalculates material quantities and labour (manual quantities are kept). Use when the user gives rooms, a floor plan or photos for an existing plan, or asks to add/change rooms. view_id from show_renovation_plan / open_plan. Send the FULL room list (it replaces the old one). save_only: true stores rooms without recalculating. The updated plan is shown to 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>",
      "rooms": "<rooms>"
    },
    "name": "recalc_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomsYes
view_idYes
height_mNo
save_onlyNoOnly store rooms, no recalculation
total_area_m2No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the most consequential behavior: the rooms array REPLACES the previous list, manual quantities are preserved through recalculation, save_only skips recalc, and the updated plan is displayed to the user. These are the facts an agent needs to avoid silent data loss, which readOnlyHint/destructiveHint alone do not convey.

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?

Front-loaded with the action and its scope, then triggers, then prerequisites, then the critical 'send the FULL room list' warning. Dense em-dash lists make it slightly harder to scan, but no sentence 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?

For a 5-parameter mutation tool with no output schema, it covers the destructive replacement semantics, the recalc side effects, and where view_id comes from. Only the two undocumented numeric parameters keep it from being fully 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 only 20%, so the description carries the load and mostly does: it explains each room field (name, area_m2 or length_m × width_m, floor type, wet bathroom, level, ceiling height), the view_id source, and save_only's meaning. It leaves total_area_m2 and the top-level height_m unexplained, which is the only real gap.

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?

States a specific verb and resource ('Sets or changes the rooms of an already shown plan') and enumerates exactly which room attributes it accepts. An agent can distinguish it from show_renovation_plan (viewing) and update_plan_items (item-level edits) without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit triggers ('user gives rooms, a floor plan or photos for an existing plan, or asks to add/change rooms'), names the prerequisite source for view_id (show_renovation_plan / open_plan), and states the alternative behavior via save_only: true.

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