Skip to main content
Glama

Open 3D configurator

open_configurator
Read-onlyIdempotent

Shows the interactive BandFactory wristband configurator with a rotatable 3D preview, prefilled with the given design (all fields optional). The customer can change style, text, font, colours, flag or symbol, size, quantity and extras, sees the live price and orders on bandfactory.eu. Also returns the current design, price and design link as text.

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_configurator"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagNoCountry or symbol flag printed next to the text (ISO code, pride or peace). Not together with symbol.
fontNoFont family. Some fonts are only available for the printed style.
glowNoGlow-in-the-dark silicone.
styleNoFinish: printed (flat, colour print), debossed_filled (engraved, colour-filled), debossed (engraved, no fill), embossed_printed (raised and printed), embossed (raised, no fill).
repeatNoHow often text and symbol repeat around the band (default 1).
symbolNoIcon in the text colour, e.g. heart, star, football. Not together with flag.
countryNoDelivery country (ISO code). Prices include that country's VAT.DE
glitterNoGlitter (sequins) in the silicone.
rainbowNoSegmented rainbow band (6 colours) instead of one band colour.
qty_kidsNoOptional, to mix sizes: number of Kids bands (152 mm).
quantityNoNumber of wristbands. Larger orders are quoted on request.
width_mmNoBand width in mm (default 12).
packagingNoEach band individually packed.
qty_youthNoOptional, to mix sizes: number of Youth bands (180 mm).
band_colorNoBand colour as hex, e.g. #005eb8.
text_colorNoColour of the outside text, symbol and fill, as hex.
text_insideNoOptional text on the inside of the band.
band_pantoneNoOptional Pantone code for the band colour, e.g. 300 C.
qty_standardNoOptional, to mix sizes in one order: number of Standard bands (202 mm). Together with qty_youth and qty_kids this replaces quantity (quantity becomes the sum). Each additional size costs a one-off fee for its own print mould.
text_outsideNoText on the outside of the band.
circumference_mmNoInner circumference in mm (default 202, adult).
text_color_insideNoColour of the inside text, as hex.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / qty_kids
      Added value: +{
      +  "description": "Optional, to mix sizes: number of Kids bands (152 mm).",
      +  "maximum": 9998,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / qty_standard
      Added value: +{
      +  "description": "Optional, to mix sizes in one order: number of Standard bands (202 mm). Together with qty_youth and qty_kids this replaces quantity (quantity becomes the sum). Each additional size costs a one-off fee for its own print mould.",
      +  "maximum": 9998,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / qty_youth
      Added value: +{
      +  "description": "Optional, to mix sizes: number of Youth bands (180 mm).",
      +  "maximum": 9998,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the customer can go on to change attributes and place an order on bandfactory.eu, the price updates live, and the tool additionally returns design, price and design link as text. The one gap is that 'shows the interactive ... 3D preview' could mislead an agent into thinking it receives a visual artefact, when the callable output is text.

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?

Three sentences, front-loaded with the identity of the tool and what it renders, then the interactive capability, then the return value. No filler or repetition of the title. The middle sentence is a little long and enumerates customer-facing options at more length than an agent needs.

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 22 optional parameters and no output schema, the description does the necessary work of explaining that the call returns the current design, price and design link as text — without that, an agent might expect a rendered UI handle or nothing at all. It covers the prefill contract and the resulting side effect (the customer may order externally). Only the precise shape of the textual return is left vague.

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 coverage is 100% across 22 parameters, so the schema already documents enums, ranges, defaults and constraints in detail. The description only categorises the fields loosely (style, text, font, colours, flag or symbol, size, quantity and extras), which adds no format or interaction detail — notably the flag/symbol exclusivity is stated in the schema, not here. Baseline 3 applies when the schema does the heavy lifting.

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: shows the interactive BandFactory wristband configurator with a rotatable 3D preview, prefilled from arguments. That is far more than a restatement of the name. It does not, however, distinguish itself from siblings whose functions it overlaps (get_price_quote, create_design_link, get_options), all of which it silently also performs.

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?

The parenthetical '(all fields optional)' tells the agent the call is valid with no arguments and that partial prefills are acceptable, which is genuine usage guidance. Beyond that, there is no statement of when to call this versus get_options, get_price_quote, or create_design_link — an agent cannot tell from this text which of those to reach for. Usage is implied rather than directed.

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