Lustrix – mirrors made to measure

Price a mirror made to measure

quote_mirror

Read-onlyIdempotent

Prices one mirror exactly as the shop does: product gross price with its option lines, weight, delivery methods with rate-table prices (add postalCode for a delivery estimate), the cheapest total, the delivery window and whether it can be ordered. An estimate: the binding price is shown at checkout on lustrix.eu. Only include paid options the customer asked for.

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": {
      "materialSlug": "<materialSlug>",
      "shape": "<shape>",
      "widthCm": "<widthCm>"
    },
    "name": "quote_mirror"
  }
}

Input Schema

Name	Required	Description	Default
`edge`	No	grind (polished, default) or bevel	grind
`frame`	No	Paid option: a slim matte black aluminium frame (rectangle/square mirrors only). Set ONLY when the customer explicitly asked for a frame; omit otherwise (frameless is the default). Check list_options.frame.available first. With a frame, widthCm × heightCm is the outer frame size, the edge is a hidden technical grind (edge: grind; no bevel), and holes, LED, heating mat, switch and tempering are not available.
`holes`	No	Mounting holes, at most 4
`shape`	Yes	Shape id from list_options
`locale`	No	Language of every text in the answer: pl (Polish shop, PLN) or de (German shop for DE/AT, EUR). Default pl.	pl
`country`	No	Delivery country. PL with locale pl; DE or AT with locale de. Default: the shop home country.
`widthCm`	Yes	Width in cm; for a circle the diameter
`heightCm`	No	Height in cm (not for a circle; a square may omit it)
`tempered`	No	Tempered safety glass (paid; only when the customer asks)
`height2Cm`	No	Height of the second vertical side in cm, trapezoid shapes only
`backlitLed`	No	LED behind the mirror lighting the wall (paid; only when asked). Mirrors only: not for glass
`heatingMat`	No	Anti-fog heating mat (paid; only when asked). Mirrors only: not for glass
`postalCode`	No	Delivery postal code (PL 00-000, DE 12345, AT 1234). Only used to estimate delivery; never stored.
`safetyFilm`	No	Paid option: a safety backing film on the back of the mirror (if the mirror breaks, most fragments stay on the film; it does not make the mirror unbreakable), priced per m² of the mirror; mirrors only. Set ONLY when the customer explicitly asked for it; omit otherwise. Check list_options.safetyFilm.available first, and its note for whether it is available with a frame or with the heating mat.
`switchType`	No	Switch, only together with an LED (paid). Mirrors only: not for glass
`frontlitLed`	No	LED shining through a sanded stripe on the mirror face (paid; only when asked). Mirrors only: not for glass. Patterns per shape: list_options
`bevelWidthMm`	No	Bevel width in mm (5-30); required with edge=bevel
`materialSlug`	Yes	Material slug from list_materials

Output Schema

Name	Required	Description	Default
`frame`	No
`lines`	Yes
`notes`	Yes
`shape`	Yes
`locale`	Yes
`country`	Yes
`currency`	Yes
`delivery`	Yes
`estimate`	Yes
`material`	Yes
`weightKg`	Yes
`orderable`	Yes
`orderBlock`	No
`dimensionsCm`	Yes
`productBrutto`	Yes
`shipmentClass`	Yes
`deliveryWindow`	Yes
`estimatedTotalBrutto`	Yes
`finalPriceAtCheckout`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 1, 2026

changedInput schema / properties / backlitLed / description

Previous value: -"LED behind the mirror lighting the wall (paid; only when asked)"New value: +"LED behind the mirror lighting the wall (paid; only when asked). Mirrors only: not for glass"

changedInput schema / properties / frontlitLed / description

Previous value: -"LED shining through a sanded stripe on the mirror face (paid; only when asked). Patterns per shape: list_options"New value: +"LED shining through a sanded stripe on the mirror face (paid; only when asked). Mirrors only: not for glass. Patterns per shape: list_options"

changedInput schema / properties / heatingMat / description

Previous value: -"Anti-fog heating mat (paid; only when asked)"New value: +"Anti-fog heating mat (paid; only when asked). Mirrors only: not for glass"

changedInput schema / properties / switchType / description

Previous value: -"Switch, only together with an LED (paid)"New value: +"Switch, only together with an LED (paid). Mirrors only: not for glass"

Changed4 schema fields changedOct 25, 2026

changedInput schema / properties / frame / description

Previous value: -"Paid option: a slim matte black aluminium frame (rectangle/square mirrors only). Set ONLY when the customer explicitly asked for a frame; omit otherwise (frameless is the default). Check list_options.frame.available first. With a frame, widthCm × heightCm is the outer frame size."New value: +"Paid option: a slim matte black aluminium frame (rectangle/square mirrors only). Set ONLY when the customer explicitly asked for a frame; omit otherwise (frameless is the default). Check list_options.frame.available first. With a frame, widthCm × heightCm is the outer frame size, the edge is a hidden technical grind (edge: grind; no bevel), and holes, LED, heating mat, switch and tempering are not available."

addedInput schema / properties / safetyFilm

Added value: +{
+  "description": "Paid option: a safety backing film on the back of the mirror (if the mirror breaks, most fragments stay on the film; it does not make the mirror unbreakable), priced per m² of the mirror; mirrors only. Set ONLY when the customer explicitly asked for it; omit otherwise. Check list_options.safetyFilm.available first, and its note for whether it is available with a frame or with the heating mat.",
+  "type": "boolean"
+}

addedOutput schema / properties / frame / properties / edge
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / frame / required

Previous value: -[
-  "type",
-  "hanging",
-  "productionBusinessDays"
-]New value: +[
+  "type",
+  "hanging",
+  "productionBusinessDays",
+  "edge"
+]

Changed2 schema fields changedOct 20, 2026

addedInput schema / properties / frame

Added value: +{
+  "description": "Paid option: a slim matte black aluminium frame (rectangle/square mirrors only). Set ONLY when the customer explicitly asked for a frame; omit otherwise (frameless is the default). Check list_options.frame.available first. With a frame, widthCm × heightCm is the outer frame size.",
+  "enum": [
+    "alu-black-matte"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / frame

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "hanging": {
+      "enum": [
+        "vertical",
+        "horizontal"
+      ],
+      "type": "string"
+    },
+    "productionBusinessDays": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "type": {
+      "enum": [
+        "alu-black-matte"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "type",
+    "hanging",
+    "productionBusinessDays"
+  ],
+  "type": "object"
+}

First observedOct 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With readOnly/idempotent annotations already covering safety, the description adds the important behavioral caveat that this is an estimate and 'the binding price is shown at checkout on lustrix.eu'. It also previews the returned quote components. It does not mention error behavior for invalid configurations, but that is a minor remaining gap against annotated safety.

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 sentences, front-loaded with the pricing action, followed by the estimate caveat and the paid-options selection rule. No waste and no repetition of schema detail.

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?

Given 18 parameters, an output schema, and full schema descriptions, the description covers purpose, the estimate-vs-binding distinction, and a key configuration rule. It does not explicitly flag the prerequisite of sourcing materialSlug and shape from list_materials/list_options, which would help an agent sequence calls correctly.

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 description coverage is 100% and the schema already documents fields, enums, defaults, and constraints in depth. The description's only parameter-adjacent additions are the postalCode hint and the paid-options rule, both of which are already stated in the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('Prices one mirror exactly as the shop does') and enumerates the returned quote components (gross price, weight, delivery methods, cheapest total, delivery window, orderability). It is clearly distinct from lookup siblings like list_materials and list_options, but it never names or contrasts those siblings explicitly, so it stops short of the top band.

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

Usage Guidelines3/5

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

Provides one explicit usage rule ('Only include paid options the customer asked for') and tells the agent when to add postalCode for a delivery estimate. It does not state when to choose this tool over calling list_options or list_materials first, nor any exclusion conditions, so usage is only implied.

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

All Lustrix – mirrors made to measure tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?