Skip to main content
Glama

Create design link

create_design_link
Read-onlyIdempotent

Returns a link to the BandFactory configurator prefilled with the given wristband design, where the customer can preview it in 3D, upload a logo and order. Includes the total price. In clients that display apps it also shows the design in the 3D configurator.

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": {
      "style": "<style>",
      "quantity": "<quantity>"
    },
    "name": "create_design_link"
  }
}

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.
styleYesFinish: 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).
quantityYesNumber 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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by saying the return is a link that also carries the total price and, in app-capable clients, embeds the 3D configurator. It omits link lifetime, whether the design is persisted server-side, and what happens if the customer never completes the order.

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 short sentences, front-loaded with the return value, then the price and the in-client rendering behavior. No filler, though the third sentence about clients that display apps is a niche detail that could be trimmed.

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 parameters, no output schema, and only a read-only annotation set, the description carries the burden of explaining the return value, which it does: a prefilled configurator link plus total price. The main remaining gap is link validity or expiry, which matters for a link the customer is expected to act on later.

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 22 parameters, including the mutual exclusion between flag and symbol and the quantity-vs-qty_* size-mixing rules. The description adds no parameter-level meaning beyond 'the given wristband design', so the baseline of 3 applies.

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?

The description gives a specific verb and resource: it returns a configurator link prefilled with a wristband design, plus the total price. It is clear enough to distinguish from data-returning siblings like get_options or get_price_quote, but it never mentions open_configurator, which sounds like the closest neighbor.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The description implies a customer-facing preview/order flow, but with a sibling named open_configurator and another named get_price_quote, an agent gets no rule for choosing between them.

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