Skip to main content
Glama

Remont — renovation planner

Prepare renovation plan data

prepare_plan
Read-only

In one request: country profile (stores, rules, currency), stages with tasks and tools, material calculation by room and for every material and tool — ready products from the country catalog (by tier standard/premium/lux, with price and link). Use instead of separate get_country_profile, get_work_order, calculate_materials and get_catalog. todo lists what still has to be found in stores.

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": {
      "country": "<country>",
      "works": "<works>"
    },
    "name": "prepare_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
modeNo
tierNoDefault tier
doorsNo
roomsNo
worksYes
boilerNoHeat source: gas — system boiler + cylinder + flue, combi — combi boiler + flue, furnace — US gas furnace + central AC + water heater, heat_pump — heat pump + cylinder, none. Omit to use the country default
floorsNo
stairsNo
countryYesISO country code
windowsNoWindows, pcs (for window sills)
attic_m2No
height_mNoCeiling height, m (default for rooms)
propertyNo
facade_m2No
kitchen_mNoKitchen length, running m (default 3.5)
ui_localeNoLanguage of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
user_codeNoUser's personal code, if known — applies their saved preferences (owned tools, preferred products) by default
new_pointsNo
total_area_m2No
distribution_boardNoA new consumer unit is needed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral context — it is a single aggregate call rather than four, and the response includes a 'todo' of items still to be sourced in stores. It does not clarify whether anything is persisted or how large the response is, which matters for a 21-parameter aggregator.

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?

It is short, but the opening sentence is a dense run-on list of outputs joined by em-dashes and commas that takes effort to parse. The trailing 'todo lists what still has to be found in stores' reads as an afterthought rather than being integrated with the other output fields.

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

Completeness3/5

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

There is no output schema, and the description does helpfully sketch the return payload (profile, stages, materials, catalog products, todo). But for a tool with 21 inputs and nested room objects, the description leaves most input semantics and any size/pagination expectations unexplained, so it is only partly complete for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 21 parameters and only 43% schema description coverage, the description needs to carry weight but instead adds almost nothing: it echoes 'tier' (standard/premium/lux) and mentions country, and says nothing about works, rooms, boiler, ui_locale, user_code, distribution_board, or the area/height defaults. An agent must read the schema for nearly all input meaning.

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 states concretely what the tool assembles: country profile, staged tasks/tools, per-room material calculation, and catalog products with price and link. It distinguishes itself from siblings by naming the four tools it replaces. The verb is implicit ('prepare' only in the title), which keeps it from 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 Guidelines4/5

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

It gives an explicit routing rule: 'Use instead of separate get_country_profile, get_work_order, calculate_materials and get_catalog.' That is a real when-to-use statement against named alternatives. It does not say when NOT to use it (e.g. when an existing plan should be fetched via get_plan/open_plan instead), so it stops short of a 5.

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