Skip to main content
Glama

Remont — renovation planner

Show renovation plan

show_renovation_plan
Read-only

Shows the user an interactive plan: stages with a checklist and a materials table with the estimate. All texts in the user's language.

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": {
      "title": "<title>",
      "locale": "<locale>",
      "currency": "<currency>",
      "stages": "<stages>",
      "materials": "<materials>"
    },
    "name": "show_renovation_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoWho does the work
notesNo
roomsNoRooms (name, area_m2, length_m, width_m, floor, wet) if you have no calc_input
titleYes
toolsNoTools for DIY work, by stage
labelsNoWidget text translations for languages without a built-in translation (built in: ru, pl, en, de, uk). Keys come from get_ui_labels.
localeYesLanguage of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
stagesYes
countryNoISO country code — needed so the plan can fill in prices itself
view_idNoOnly if you re-show the same plan
currencyYesISO currency code, e.g. PLN
materialsYes
user_codeNoUser's personal code, if known — applies saved preferences by default
calc_inputNocalc_input from prepare_plan, unchanged — REQUIRED for the rooms editor: rooms, sizes and ceiling height are stored with the plan
default_tierNoTier selected by default for all stages
prices_checked_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 genuinely useful context beyond them: the result is an interactive UI shown to the user rather than returned data, and all texts render in the user's language. It does not disclose whether the plan is persisted, what happens on repeated calls, or how view_id affects re-display.

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?

Two short sentences, front-loaded with the core action and the rendered contents, with the localization note last. No filler, though the second sentence is more of a constraint than a description of the tool's role.

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?

For a 16-parameter widget-rendering tool with no output schema, the schema carries most of the burden and the annotations cover the read-only profile. Still missing is any statement of workflow position (prepare_plan → show_renovation_plan), re-display semantics via view_id, and whether this persists anything, which matters at this complexity level.

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 16 parameters, nested objects and only 69% schema description coverage, the description contributes almost nothing beyond the schema. Apart from implying the locale governs all rendered texts, it explains no parameter behavior (view_id reuse, user_code preferences, default_tier, prices_checked_at) that the schema itself does not already cover.

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 names a concrete verb and resource ('Shows the user an interactive plan') and specifies the two rendered components (stages with checklist, materials table with estimate). It is clear what the tool produces, but it never differentiates itself from near-name siblings such as open_plan, get_plan or save_plan.

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 when-to-use guidance at all: the description does not say to call this after prepare_plan, nor when to prefer it over open_plan/get_plan/save_plan, nor when a view_id re-show is appropriate. The only actionable hint ('All texts in the user's language') is a locale note, not usage guidance.

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