Skip to main content
Glama

Get the window preview

get_visualiser_preview

Draw and return the preview for a job_id from start_visualiser_preview: the blind in the chosen colour on the customer's photo, as an image in the result and as image_url (kept 7 days). The first call draws it (30 to 90 s; outdoor up to 2 minutes); status "drawing" means call again after retry_after_seconds.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_visualiser_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault
noteNo
errorNo
colourNo
job_idYes
statusYes
checkedNo
image_urlNo
image_mimeNo
product_idNo
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behaviour beyond the annotations: the first call triggers the render (explaining the readOnlyHint=false on a 'get' tool), generation costs 30-90 s and up to 2 minutes for outdoor scenes, the result arrives both inline as an image and as image_url retained for 7 days, and there is an explicit polling loop. This is exactly the latency, side-effect and retry context annotations cannot convey.

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?

Two dense sentences with no filler: the action and output come first, then latency and the polling rule. Every clause (colour, customer photo, 7-day retention, timing) is operational information 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?

An output schema exists, so return shape need not be re-explained, and the description still covers the prerequisite, latency, polling and URL lifetime. It leaves unaddressed what happens on failure or once the job or URL expires, which is the remaining gap for a long-running render tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden for the single job_id parameter — and it does, by naming its origin (the start_visualiser_preview job) so the agent knows what value to pass. It omits any statement about format or what happens with an expired/unknown job_id.

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 ('Draw and return the preview') and ties it precisely to the job_id produced by start_visualiser_preview, describing exactly what the returned image depicts (the blind in the chosen colour on the customer's photo). This is enough to distinguish it from siblings like get_ar_visualizer_url without opening any schema.

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?

Makes the prerequisite explicit ('a job_id from start_visualiser_preview') and gives concrete polling guidance: a status of 'drawing' means call again after retry_after_seconds. It does not state when to prefer this over the AR URL sibling, so it stops short of explicit alternatives.

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