Lustrix – mirrors made to measure

Save the design and get the order link

create_design_link

Saves the priced mirror as a design on lustrix.eu and returns two links: the configurator (to review or change it) and the checkout (to order it), plus the same price block as quote_mirror. The customer orders and pays on lustrix.eu; nothing is ordered by this tool. The design is deleted after 30 days if not ordered.

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": "create_design_link"
  }
}

Input Schema

Name	Required	Description	Default
`edge`	No	grind (polished, default) or bevel	grind
`name`	No	Design name shown in the shop (max 60 characters). No personal data.
`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
`notes`	No	Notes for the workshop (max 500 characters). No personal data.
`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
`designId`	Yes
`estimate`	Yes
`material`	Yes
`nextStep`	Yes
`weightKg`	Yes
`orderable`	Yes
`orderBlock`	No
`checkoutUrl`	Yes
`configureUrl`	Yes
`dimensionsCm`	Yes
`expiresInDays`	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

A4.2/5.0

Behavior4/5

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

Annotations already flag a non-read-only, non-idempotent write; the description adds valuable context beyond them: the order happens externally on lustrix.eu, no order is placed by this call, and the persisted design is deleted after 30 days if unordered. It does not mention that repeated calls create separate designs (non-idempotency consequence), which would have closed the gap entirely.

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 tight sentences: what it does and returns first, then the external-order disclaimers and retention limit. No repetition of schema content, no filler.

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 20-parameter write tool with an output schema and full schema coverage, the description covers the essential lifecycle facts (no order placed, 30-day expiry, link return type). A note on idempotency implications or prerequisites from quote_mirror would make it complete, but nothing an agent needs to invoke it correctly is missing.

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% across 20 well-documented parameters, so the schema carries the semantics and the baseline of 3 applies. The description adds no parameter-level guidance (e.g., that inputs should mirror the validated quote configuration).

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 ('Saves the priced mirror as a design on lustrix.eu') and specifies the exact outputs (configurator link, checkout link, price block). It explicitly positions itself against quote_mirror by saying it returns the same price block, so the agent can distinguish the two without opening schemas.

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?

The pairing with quote_mirror and the note that 'nothing is ordered by this tool' makes clear this is the post-quote, pre-order step. However, it never explicitly says 'call quote_mirror first' or 'use this only when the customer is ready to order', so the sequencing is inferred rather than stated.

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?