Skip to main content
Glama

Get a painted photo

get_visualization
Read-onlyIdempotent

Paid tools. Fetch the colours of a visualize_room job that were not ready yet, by job_id and project_id. Waits up to about 25 seconds. Costs nothing extra.

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>",
      "project_id": "<project_id>"
    },
    "name": "get_visualization"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesjob_id from visualize_room
countryNoWhere the user buys paint, e.g. "PL", "DE", "US": brands sold there come first in the shopping list
matchesNoPaints to list per colour (default 5, 0 = no shopping list)
project_idYesproject_id from visualize_room
match_brandsNoOnly list paints from these brands, e.g. ["Dulux", "Śnieżka"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 open-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the call blocks for up to roughly 25 seconds and incurs no extra cost beyond the base paid tool. It does not say what happens on timeout, but the latency disclosure is the key operational fact an agent needs.

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?

Four short sentences, front-loaded with the identity of the resource and then the operational facts (wait time, cost). The only waste is the cryptic opener 'Paid tools.', which sits oddly next to the later 'Costs nothing extra.' and could confuse a reader about pricing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must characterize the return value, and it only says 'the colours' without describing the shape or whether a shopping list accompanies them (the matches/match_brands parameters imply one). It also omits the fallback when the ~25 second wait expires. Adequate but with clear gaps for a tool with five parameters.

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%, so every parameter including country, matches and match_brands is already documented in the schema. The description only names job_id and project_id, both of which are already described, and adds no new semantics. Baseline 3 is appropriate 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?

The description gives a specific verb and resource: fetch the colours of a visualize_room job that were not ready yet, keyed by job_id and project_id. It ties itself to the sibling visualize_room, so an agent can see this is the follow-up/polling step rather than the job-creation step. The leading fragment 'Paid tools.' is ambiguous phrasing that slightly muddies the opening.

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?

Use is implied: call this for a visualize_room job whose colours were not ready yet, which signals the post-creation polling context. However, there is no explicit when-not guidance (e.g. what to do if results are still not ready after the wait) and no named alternative for other colour lookups such as get_paint_color or search_paint_colors.

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