Skip to main content
Glama

Interior design (Interior AI)

luw_interior_design

Redesign an interior photo in any style while preserving the room's architecture, including furniture, materials, colors, and lighting; furnish empty rooms or convert them to another room type.

Instructions

Luw.ai Interior AI: redesign an interior photo — home, office, shop, hotel — in any style while keeping the room's architecture. Restyles furniture, materials, colors and lighting. Set empty_room=true to furnish an empty room or turn it into another room type (virtual staging). 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_interior_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesPhoto of the room (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 much to change: 80+ subtly, 50-79 moderately (default 50), under 50 dramatically. Applies when prompt is empty, with style_reference, or when furnishing an empty room.
room_typeNoRoom type, e.g. "Living Room", "Kitchen", "Bedroom", "Home Office" (see luw_list_options kind="interior_types").
empty_roomNoFurnish from scratch / convert the room to room_type (Fill Empty Room mode).
persona_idNoPersona whose saved images to use. Its saved styles and room or building type apply unless you send styles or a type.
variationsNoNumber of alternative designs (1-4, default 1); each is billed as a generation.
enhance_promptNoLet Luw.ai write the design brief when prompt is empty and there is no style_reference. A written prompt is used as written.
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.
reference_imagesNoUp to 6 reference images (furniture, materials, products, mood boards) to draw from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.3.18
    • changedInput schema / properties / enhance_prompt / description
      Previous value: -"Let Luw.ai's prompt enhancer expand a short prompt."New value: +"Let Luw.ai write the design brief when prompt is empty and there is no style_reference. A written prompt is used as written."
    • changedInput schema / properties / image / description
      Previous value: -"Photo of the room (https:// URL, local file path, or data: URI)."New value: +"Photo of the room (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 much to change: 80+ subtly, 50-79 moderately (default 50), under 50 dramatically. Applies when prompt is empty, with style_reference, or when furnishing an empty room."
    • 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)."
    • 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.8/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, so the agent knows this is a non-destructive generative call. The description adds real value beyond them with the billing rule ('Costs 1 credit per variation') and the empty_room mode switch. It says nothing about whether the call is synchronous, how long it takes, or how results are retrieved, which matters for a generation endpoint.

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?

Three sentences, front-loaded with the verb and the core constraint, then the mode switch, then the cost. Minor waste in the redundant 'Luw.ai Interior AI:' prefix that restates the title, but nothing else is padding.

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 generative tool with no output schema, the definition covers the core action well but omits the surrounding workflow — whether the response is immediate or must be collected via luw_get_result, and how long generations typically take. That omission is the main thing an agent needs before invoking it.

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 the schema already explains every parameter, including precision thresholds, valid enums, and the Japandi style pairing. The description only re-frames empty_room and variations (billing) rather than adding new parameter meaning, so the baseline of 3 applies.

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+resource ('redesign an interior photo') plus the exact transformation ('Restyles furniture, materials, colors and lighting') and the invariant ('keeping the room's architecture'). The word 'interior' plus the room examples (home, office, shop, hotel) separate it from the exterior/landscape siblings without needing to name them.

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 a concrete routing rule for the ambiguous case: 'Set empty_room=true to furnish an empty room or turn it into another room type (virtual staging)'. It also points at luw_list_options for valid style and room_type values. It does not state when to use a sibling instead (e.g. exterior vs interior) or any prerequisites/auth, so it falls short of a 5.

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