Skip to main content
Glama

Get the web visualiser link

get_ar_visualizer_url
Read-only

Returns the link to the Custom Blinds Visualiser (See it before you buy it), pre-selected to the product when it is supported. The customer adds a photo of their window (any angle), picks a blind and colour, and previews it on their own window. A preview of colour and style, not a measuring tool. No measuring or marking. A name and WhatsApp number are needed; 2 free previews per customer. Also returns the measuring guide (mode 'measure' makes it the main url) and the list of supported products. A customer still unsure of sizes can order with best guess sizes, receive a free tape measure and confirm before production starts. Use when a customer wants to see how a blind or colour will look before ordering, or is unsure how to measure. If you already have the customer's photo, use start_visualiser_preview to show the blind in this chat instead.

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

Input Schema

NameRequiredDescriptionDefault
modeNoWhich link goes in url: visualize (own-window visualiser), measure (measuring guide) or both (visualiser, the default). Both links are always returned.
product_idNoOptional. Pre-select a product in the visualiser (e.g. roller-blockout, double-roller-zebra, outdoor-blinds).

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
product_idNo
measure_urlYes
visualiser_urlYes
supported_productsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare this is a safe read, so the description carries real weight and delivers: preconditions (a name and WhatsApp number are required), a quota (2 free previews per customer), and the fact that the call also returns the measuring guide and the supported-product list. The mode-dependent URL behaviour adds operational context the annotations cannot express.

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?

The purpose and the sibling alternative are front-loaded, but the middle drifts into sales-process narrative ('order with best guess sizes, receive a free tape measure and confirm before production starts') that does not help an agent decide or invoke. Two core sentences are padded into roughly six.

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 two-parameter read-only tool with a full output schema, this covers what an agent actually needs: when to call it, the customer prerequisites, the free-preview cap, and what else comes back. Only the off-topic order fallback keeps it short of fully earned completeness.

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% and the schema already explains that mode picks which link lands in url and that both links are always returned, so the description largely restates it. Marginal added value: the mention that measure 'makes it the main url' reinforces the default-vs-override distinction, and product_id pre-selection is illustrated with concrete product slugs.

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 ('Returns the link to the Custom Blinds Visualiser') and immediately narrows scope: 'pre-selected to the product when it is supported.' It also sets a boundary the agent needs — 'A preview of colour and style, not a measuring tool' — so it cannot be mistaken for validate_measurement.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use when a customer wants to see how a blind or colour will look before ordering, or is unsure how to measure') and names the alternative plus the condition that selects it: 'If you already have the customer's photo, use start_visualiser_preview to show the blind in this chat instead.' That is genuine routing, not implied usage.

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