Skip to main content
Glama

WELANDA Engraving Designer

Render preview

render_preview
Idempotent

Render watermarked PNG preview(s) of a VALID design (all zones, or one via zoneId). Returns preview image URLs plus the watermarked preview as inline image content (one per zone) - show it to the user. If the render queue is busy it returns {status:"pending", retryAfterSec} - retry after that delay.

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": {
      "designId": "<designId>"
    },
    "name": "render_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneIdNoRender a single zone; omit to render all zones.
designIdYesThe dsg_… id to render.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the return shape (preview URLs plus inline watermarked image content, one per zone) and a non-obvious failure mode ({status:"pending", retryAfterSec}). It does not explain why readOnlyHint=false for an idempotent, non-destructive operation (presumably a stored render artifact), which is the one behavioral gap.

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?

Three tight sentences with the core action, the output contract, and the retry path front-loaded in that order. No filler or redundant phrasing.

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

Completeness5/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 carries the return-value burden and does so: URLs, inline image content, per-zone cardinality, and the pending/retry state. An agent has everything it needs to call this and interpret the result.

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 both parameters are fully documented in the schema, and the description largely restates zoneId's effect ('all zones, or one via zoneId'). The only added meaning is the implicit requirement that the design be valid, which is undefined.

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 ('Render watermarked PNG preview(s) of a VALID design') with scope ('all zones, or one via zoneId'), which clearly separates it from the sibling set of design CRUD/link/upload tools. Nothing about the purpose needs inferring.

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?

Gives concrete operating guidance: omit zoneId to render all zones, show the inline image to the user, and retry after retryAfterSec when the queue is busy. There is no explicit exclusion or named alternative, but no sibling competes for the same job, so the guidance is sufficient.

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