Skip to main content
Glama

Remont — renovation planner

Open renovation questionnaire

open_questionnaire
Read-only

Shows the user a form: apartment or house, renovation type, city, rooms, works, who does them. Call when data about the property is missing. The answers arrive in the user's next message as JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_questionnaire"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
roomsNoRooms recognised from the user's floor plan or photos
floorsNo
labelsNoWidget text translations for languages without a built-in translation (built in: ru, pl, en, de, uk). Keys come from get_ui_labels.
localeNoLanguage of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
countryNoCountry code, if known
height_mNo
propertyNo
total_area_m2No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description adds real value by disclosing the interaction model: the tool surfaces a form to the user and returns nothing itself — the answers arrive as JSON in the user's next message. That is the single most important behavioral fact and it is stated plainly. It does not say whether calling it interrupts an in-flight workflow or whether prefilled values are shown to the user.

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?

Three short sentences: what it shows, when to call it, and how the result comes back. The most decision-relevant facts are front-loaded and nothing is repeated or padded.

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?

With 9 optional params, nested room objects, and no output schema, the description covers the essentials by explaining the asynchronous answer mechanism, which no structured field conveys. The gap is that it never clarifies how the supplied params interact with the form or whether any of them are mandatory despite zero required fields.

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?

The field list implies that the parameters prefill the form, which is genuine meaning beyond the schema, and several listed items map to params (property, city, rooms). However, schema coverage is only 44 percent, and the description says nothing about locale, labels, floors, height_m, or total_area_m2 — notably the 'Always pass it' locale requirement stays buried in the schema. It also lists 'renovation type' and 'works, who does them', which have no obvious corresponding schema property, leaving the mapping ambiguous.

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 ('Shows the user a form') and enumerates the form's fields, so the agent immediately understands this is a UI-opening tool rather than a data-fetching one. That verb choice alone separates it from the surrounding get_/save_/plan_ 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?

'Call when data about the property is missing' gives an explicit trigger condition, which is the key routing rule for this tool. It stops short of naming the alternative path (e.g. proceeding with open_plan when data is already known) or stating whether it can be called mid-plan, so it is clear but not exhaustive.

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