Skip to main content
Glama

Remont — renovation planner

Calculate materials

calculate_materials
Read-only

Calculates material quantities with waste allowance per room. Returns material keys and search queries in the language of the country's 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>",
      "rooms": "<rooms>",
      "works": "<works>",
      "mode": "<mode>"
    },
    "name": "calculate_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesdiy — do it yourself, pro — contractor
doorsNo
roomsYes
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
stairsNo
countryYesISO country code
windowsNoWindows, pcs (for window sills)
attic_m2NoHouse: attic roof area to insulate, m²
propertyNo
facade_m2NoHouse: facade area without windows, m²
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.
new_pointsNoNew sockets and switches
total_area_m2No
distribution_boardNoA new consumer unit is needed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing two behaviors beyond the annotations: the waste allowance applied to quantities and that output consists of material keys plus localized search queries. However, it says nothing about determinism, units, or how the result relates to pricing, which matters for a computation tool with no output schema.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the computation and then the return content. Nothing is wasted and nothing is buried.

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 calculator with no output schema, the description should say what comes back, and it does (material keys and search queries). Given the nested 16-parameter schema is largely self-documented, this is close to complete, though it omits any note on how to chain the returned keys into price lookup or how partial inputs are handled.

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?

Schema coverage is 63%, so the schema carries most parameter documentation (mode, boiler, ui_locale, facade_m2, etc. are described inline). The description adds only indirect meaning — 'language of the country's stores' hints at how the country parameter drives output language — but does not clarify the country vs. ui_locale split or the relationship between rooms, works, and the optional house-only fields.

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 verb and resource ('Calculates material quantities') plus scope ('with waste allowance per room'), which is clearly distinct from the read/write plan-management siblings. It stops short of naming which sibling to prefer (e.g. recalc_plan or prepare_plan), so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance and no alternative is named, despite siblings like recalc_plan, prepare_plan and get_catalog that could plausibly overlap. Usage is only implied by the stated purpose.

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