Skip to main content
Glama

Configurator link with room dimensions

build_configurator_link
Read-onlyIdempotent

Creates a Vargov®Design 3D configurator link pre-filled with plan length, width, ceiling height, and optional language or form-step settings, so users can open a ready calculation.

Instructions

Builds a link that opens the Vargov®Design 3D configurator on a composition with the plan dimensions and the room ceiling height already filled in. Only codes that open with a full calculation are accepted (360 of 605; others return an error with the product page). lengthMm → the "Length" field of the plan, widthMm → the "Width" field, both integer millimetres, at least 300 (the plan is the zone the composition is laid out in, not a product size); heightMm → height of the cloud of elements (optional); ceilingMm → room ceiling height (optional, default 2700 in the configurator; it goes into the IFC4 file and AR); lang → interface language (ru opens configurator.vargov.ru, other languages vargov.design); openOnFormStep → open scrolled to the "Composition form" step. The visitor then picks element sizes, colours and the form; the configurator's "Share" button returns a link that reopens that exact calculation.

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": {
      "code": "<code>"
    },
    "name": "build_configurator_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
langNoru en de it fr es vi ar; default en
widthMmNoPlan width, integer mm, ≥ 300
heightMmNoHeight of the cloud of elements, integer mm (optional)
lengthMmNoPlan length, integer mm, ≥ 300
ceilingMmNoRoom ceiling height, integer mm (optional; configurator default 2700)
openOnFormStepNotrue: add step=form to open scrolled to the form step

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly/idempotent/closed-world; the description adds the substantive behaviour an agent cannot get there — the ~60% code acceptance rate, what happens on rejection, that language selection changes the target domain, and that the produced link is a starting point a human finishes. This is well beyond annotation coverage.

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 purpose and eligibility before parameter detail, and almost every clause earns its place. It is a single dense block, though, and repeats a few schema facts (lang enum, 2700 default), and the closing sentence about the Share button is more context than instruction.

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 seven-parameter link builder with no output schema, the description covers inputs, eligibility, error behaviour and the return artifact (a link). It never explicitly states the tool returns a URL string, and the heightMm phrasing ("cloud of elements") remains slightly opaque, leaving a small gap.

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

Parameters5/5

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

Schema coverage is already 86%, yet the description still adds meaning: it disambiguates that lengthMm/widthMm are the plan zone the composition is laid out in, not a product size, and that heightMm is the cloud-of-elements height, distinct from ceilingMm which feeds the IFC4 file and AR. It also explains the lang → domain mapping and what openOnFormStep actually scrolls to.

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 concrete verb and artifact: "Builds a link that opens the Vargov®Design 3D configurator on a composition" with dimensions pre-filled. The scope (a URL builder, not a data fetch) is unmistakable and clearly separable from siblings like get_composition or search_compositions.

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?

Gives a real eligibility rule: only codes that open with a full calculation are accepted (360 of 605), with the failure mode described (error plus product page). It also explains the downstream flow (visitor picks sizes/colours, then uses Share). It stops short of naming an alternative tool to use when a code is not eligible, so it is clear context rather than full when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.