Skip to main content
Glama
Sign In

BandFactory

by eu.bandfactory
OverviewDiscussionsAdmin

Get price quote

get_price_quote
Read-onlyIdempotent

Calculates the exact price for a silicone wristband configuration with the same calculation as the website and checkout (total, price per band, itemised fees, VAT or import charges for the delivery country) and returns the design link that opens the configurator on bandfactory.eu prefilled with this design for ordering.

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.
quantityYesNumber of wristbands. Larger orders are quoted on request.
width_mmNoBand width in mm (default 12).
packagingNoEach band individually packed.
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.
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. 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 readOnly, idempotent and non-destructive, so the safety bar is lower. The description usefully adds that the calculation matches the website/checkout and names the returned fields (total, price per band, itemised fees, VAT or import charges, design link), which is real context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single very long sentence with nested parentheses. It is front-loaded with the purpose, but dense and hard to scan; splitting return values from the calculation would improve structure.

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 19 parameters and no output schema, the description compensates by enumerating the returned price components and the design link. It omits validation caveats (quantity cap, flag/symbol exclusivity) that the schema already covers, so nothing critical 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 coverage is 100%, so all 19 parameters (enums, defaults, mutual exclusions, hex patterns, quantity cap) are already documented. The description only echoes 'delivery country' for VAT, adding no new parameter semantics.

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?

Specific verb + resource: 'Calculates the exact price for a silicone wristband configuration' and states it returns a prefilled design link. It doesn't explicitly differentiate itself from siblings like create_design_link or open_configurator, even though the design-link return overlaps with them.

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?

No explicit when-to-use or when-not guidance, and no mention of the sibling tools. The phrase 'for ordering' weakly implies it is the pre-checkout step, but the agent must infer that.

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

All BandFactory toolsInspect
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