Skip to main content
Glama

Photorealistic render (Render AI)

luw_render

Convert 3D model views, CAD/BIM screenshots, clay renders, or basic visualizations into photorealistic architectural renderings with adjustable precision and multiple variations.

Instructions

Luw.ai Render AI: turn a 3D model view, CAD/BIM screenshot, clay render or basic visualization into a photorealistic architectural render. Costs 1 credit per variation.

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": {
      "image": "<image>"
    },
    "name": "luw_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesThe 3D view or base render (public https:// link or data: URI; the local npx server also accepts a file path).
formatNoOutput image format.
promptNoWhat you want, in plain language.
precisionNoHow strictly to keep the input's structure: 90 = precise, 75 = balanced, 40 = creative.
variationsNoNumber of alternative designs (1-4, default 1); each is billed as a generation.
reference_imagesNoUp to 6 reference images (furniture, materials, products, mood boards) to draw from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.18
    • removedInput schema / properties / engine
      Removed value: -{
      -  "description": "Luw.ai model: aria (default) or symphony (Symphony-3).",
      -  "enum": [
      -    "aria",
      -    "symphony"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / properties / image / description
      Previous value: -"The 3D view or base render (https:// URL, local file path, or data: URI)."New value: +"The 3D view or base render (public https:// link or data: URI; the local npx server also accepts a file path)."
    • changedInput schema / properties / reference_images / items / description
      Previous value: -"Reference image (https:// URL, local file path, or data: URI)."New value: +"Reference image (public https:// link or data: URI; the local npx server also accepts a file path)."
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false and idempotentHint=false, so the generative, non-reversible nature is covered structurally. The description adds genuinely new information — the 1-credit cost per variation — which helps the agent budget calls. It stops short of disclosing latency, whether the call is synchronous or requires polling via luw_get_result, or what permissions/credits balance are required.

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 sentences, front-loaded with the core transformation and followed by the cost caveat. No filler, no restatement of the tool name beyond the branding prefix.

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?

The rich schema covers all six inputs, but with no output schema the description should say what comes back — an image URL, a job ID requiring luw_get_result, or a list of variations. The presence of luw_get_result among siblings makes the missing async/return-value note a meaningful gap for a 1-4 variation generative call.

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 precision, format and reference_images is already documented with ranges and examples. The description's only parameter-relevant addition is that cost scales per variation, which is a real but minor supplement. Baseline 3 is appropriate.

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?

States a concrete verb and outcome ('turn a 3D model view, CAD/BIM screenshot, clay render or basic visualization into a photorealistic architectural render') and enumerates the accepted input types. It does not explicitly distinguish itself from close siblings such as luw_sketch_to_render, so an agent must infer the boundary from input type alone.

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?

Usage context is only implied by the input listing (you should have a 3D view or base render). There is no explicit when-to-use/when-not-to-use guidance and no mention of the obvious alternative (luw_sketch_to_render) or of any prerequisite such as an uploaded image.

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