Skip to main content
Glama

Sketch to render (Sketch AI)

luw_sketch_to_render

Generate photorealistic renders from hand sketches, line drawings, floor-plan perspectives, or rough drafts, with optional prompt, style, and variation controls.

Instructions

Luw.ai Sketch AI: turn a hand sketch, line drawing, floor-plan perspective or rough draft into a photorealistic 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_sketch_to_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesThe sketch or drawing (public https:// link or data: URI; the local npx server also accepts a file path).
engineNoLuw.ai model: aria (default) or symphony (Symphony-3).
formatNoOutput image format.
promptNoWhat you want, in plain language.
stylesNoDesign style names, e.g. ["Scandinavian"]; for Japandi use ["Japanese Design", "Scandinavian"]. Case-sensitive; see luw_list_options.
precisionNoHow freely the prompt enhancer writes: 90 = precise, 75 = balanced, 40 = creative. Only used with enhance_prompt.
persona_idNoPersona whose saved images to use. Its saved styles and room or building type apply unless you send styles or a type.
space_typeNoWhat the sketch shows, e.g. "Living Room" or "Modern House Exterior".
variationsNoNumber of alternative designs (1-4, default 1); each is billed as a generation.
enhance_promptNoLet Luw.ai's prompt enhancer expand a short prompt.
style_referenceNoStyle-transfer source: an image whose look to copy (public https:// link or data: URI; the local npx server also accepts a file path), or "persona" to use slot 1 of persona_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.18
    • changedInput schema / properties / image / description
      Previous value: -"The sketch or drawing (https:// URL, local file path, or data: URI)."New value: +"The sketch or drawing (public https:// link or data: URI; the local npx server also accepts a file path)."
    • changedInput schema / properties / persona_id / description
      Previous value: -"Persona whose saved images and style knowledge to use."New value: +"Persona whose saved images to use. Its saved styles and room or building type apply unless you send styles or a type."
    • changedInput schema / properties / precision / description
      Previous value: -"How strictly to keep the input's structure: 90 = precise, 75 = balanced, 40 = creative."New value: +"How freely the prompt enhancer writes: 90 = precise, 75 = balanced, 40 = creative. Only used with enhance_prompt."
    • removedInput schema / properties / seed
      Removed value: -{
      -  "description": "Fix for reproducible results.",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / properties / style_reference / description
      Previous value: -"Style-transfer source: an image whose look to copy (https:// URL, local file path, or data: URI), or \"persona\" to use slot 1 of persona_id."New value: +"Style-transfer source: an image whose look to copy (public https:// link or data: URI; the local npx server also accepts a file path), or \"persona\" to use slot 1 of persona_id."
  2. Changed2 schema fields changedv0.3.2
    • changedInput schema / properties / persona_id / description
      Previous value: -"Persona whose saved images/knowledge to use (see luw_personas)."New value: +"Persona whose saved images and style knowledge to use."
    • changedInput schema / properties / styles / description
      Previous value: -"Design style names, e.g. [\"Japandi\"]. Case-sensitive; see luw_list_options."New value: +"Design style names, e.g. [\"Scandinavian\"]; for Japandi use [\"Japanese Design\", \"Scandinavian\"]. Case-sensitive; see luw_list_options."
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, open-world generation call, so the safety profile is covered. The description adds genuinely useful context — 1 credit per variation, meaning a 4-variation call costs 4 credits — but says nothing about whether the call returns inline or must be polled via luw_get_result, which is the most consequential unknown for a generation tool.

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 tight sentences: the capability first, the cost second. Nothing is padded and the most decision-relevant fact (credit cost) is surfaced immediately.

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?

For an 11-parameter, non-idempotent generation tool with no output schema, the description covers what goes in and what it costs but not what comes back or whether an async retrieval step is required. That leaves a real gap in calling the tool correctly end to end.

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% and each of the 11 parameters (engine, styles, precision, persona_id, style_reference, etc.) is documented in the schema itself. The description adds only the credit-per-variation cost mapping, so baseline 3 applies; no extra meaning is layered on the parameters.

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 specific verb and resource: converting a hand sketch, line drawing, floor-plan perspective or rough draft into a photorealistic render. The input modalities named (sketch/line drawing/floor plan) make it clearly distinct from generic render or generate tools, though it never names a sibling to contrast with.

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?

The description implies when to use it via the input types it accepts (sketch-based input), and the cost note gives a budgeting signal. But it offers no explicit when-not guidance or pointer to alternatives such as luw_render or luw_generate_image for non-sketch inputs.

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