Luw MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Exterior design (Exterior AI)

luw_exterior_design

Redesign a building exterior or facade photo in a new architectural style with updated materials, colors, and landscaping while preserving the original structure.

Instructions

Redesign a building exterior or facade photo — houses, villas, apartments, commercial buildings — in a new architectural style, with new materials, colors and landscaping, keeping the structure. Costs 1 credit per variation.

Input Schema

TableJSON Schema

Name	Required	Description
`seed`	No	Fix for reproducible results.
`image`	Yes	Photo of the building (https:// URL, local file path, or data: URI).
`engine`	No	Luw.ai model: aria (default) or symphony (Symphony-3).
`format`	No	Output image format.
`prompt`	No	What you want, in plain language.
`styles`	No	Design style names, e.g. ["Japandi"]. Case-sensitive; see luw_list_options.
`precision`	No	How strictly to keep the input's structure: 90 = precise, 75 = balanced, 40 = creative.
`persona_id`	No	Persona whose saved images/knowledge to use (see luw_personas).
`variations`	No	Number of alternative designs (1-4, default 1); each is billed as a generation.
`building_type`	No	Building/space type, e.g. "Modern House Exterior", "Luxury Villa Exterior", "Outdoor Patio" (see luw_list_options kind="exterior_types").
`enhance_prompt`	No	Let Luw.ai's prompt enhancer expand a short prompt.
`style_reference`	No	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.
`reference_images`	No	Up to 6 reference images (furniture, materials, products, mood boards) to draw from.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and non-idempotent, covering the mutation/safety profile. The description adds genuinely new behavioral context: the 1-credit-per-variation billing model and the structural-preservation constraint, which the 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 compact clauses: the action and target lead, the scope list is tightly embedded, and the cost disclosure closes. No wasted words and the most important information is front-loaded.

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 a 13-parameter generation tool with no output schema, the description covers purpose and cost but omits how results are retrieved (the sibling luw_get_result suggests an async flow) and does not point at luw_list_options for valid styles/building types. Adequate but leaves real operational gaps.

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% (13 params, each documented, two with enums), so the schema already carries parameter meaning. The description adds no parameter-level syntax, format rules, or defaults beyond that, making the baseline 3 correct.

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?

Specific verb ("Redesign") plus resource ("building exterior or facade photo") plus an enumerated scope (houses, villas, apartments, commercial buildings). The exterior/facade framing inherently distinguishes it from luw_interior_design without the agent opening either schema.

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 phrase "keeping the structure" implies this operates on an existing photo rather than generating from scratch, which softly separates it from luw_generate_image / luw_render. However, it never states when to choose this over luw_interior_design, luw_sketch_to_render, or luw_landscape_design, and offers no exclusions or prerequisites.

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

Exterior design (Exterior AI)

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools