Skip to main content
Glama
Luvi-io

Luw MCP Server

Official
by Luvi-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Interior design (Interior AI)

luw_interior_design

Redesign interior photos in any style while keeping the room's architecture. Restyle furniture, materials, colors, and lighting, or furnish an empty room.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoFix for reproducible results.
imageYesPhoto of the room (https:// URL, local file path, or data: URI).
engineNoLuw.ai model: aria (default) or symphony (Symphony-3).
formatNoOutput image format.
promptNoWhat you want, in plain language.
stylesNoDesign style names, e.g. ["Japandi"]. Case-sensitive; see luw_list_options.
precisionNoHow strictly to keep the input's structure: 90 = precise, 75 = balanced, 40 = creative.
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/knowledge to use (see luw_personas).
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 (https:// URL, local file path, or data: URI), 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. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses the credit cost (1 per variation) and what is preserved versus restyled (architecture kept; furniture/materials/colors/lighting changed).

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, each earning its place: purpose/constraint, what changes, the empty_room mode, and cost. Scoping and preservation are front-loaded before the mode instruction, so intent lands immediately.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 params but full schema coverage and no output schema, the description need not document return values or parameter syntax; it covers the purpose, the key mode toggle, and cost. It could mention the variations billing/engine choice, but the schema handles those, leaving only minor 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%, so the baseline is 3. The description only adds meaning for empty_room (virtual staging / room conversion), which largely restates the schema's own text, and says nothing about the other 13 params. It neither contradicts nor meaningfully extends the schema.

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 (redesign an interior photo) plus scope (home, office, shop, hotel) and a distinguishing constraint (keeping the room's architecture). An agent can tell this apart from exterior/landscape/archigpt siblings without opening any schema.

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 clear usage context — redesign interiors while preserving architecture — and a concrete conditional instruction (set empty_room=true to furnish or convert a room via virtual staging). It never names an alternative sibling or an explicit when-not-to-use case, so it stops 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.

Deploy Server

Other Tools