Skip to main content
Glama

Landscape & garden design (Landscape AI)

luw_landscape_design

Design a garden, yard, or outdoor area inside a masked photo region, selecting plants for the local climate and sun exposure to match the site's conditions.

Instructions

Luw.ai Landscape AI: design a garden, yard or outdoor area inside a masked region of a photo, with plants chosen for the location's climate and sun exposure. Costs 1 credit.

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>",
      "mask_image": "<mask_image>"
    },
    "name": "luw_landscape_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoLocation, for climate-appropriate planting, e.g. "Antalya".
imageYesPhoto of the outdoor area (public https:// link or data: URI; the local npx server also accepts a file path).
promptNoWhat you want, in plain language.
mask_imageYesBlack/white mask, white = area to landscape (public https:// link or data: URI; the local npx server also accepts a file path).
sun_exposureNoe.g. "Full sun (6+ hours)", "Partial sun (4 - 6 hours)", "Shade (less than 4 hours)".
enhance_promptNoLet Luw.ai's prompt enhancer expand a short prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.18
    • removedInput schema / properties / format
      Removed value: -{
      -  "description": "Output image format.",
      -  "enum": [
      -    "jpg",
      -    "png",
      -    "webp"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / properties / image / description
      Previous value: -"Photo of the outdoor area (https:// URL, local file path, or data: URI)."New value: +"Photo of the outdoor area (public https:// link or data: URI; the local npx server also accepts a file path)."
    • changedInput schema / properties / mask_image / description
      Previous value: -"Black/white mask, white = area to landscape (https:// URL, local file path, or data: URI)."New value: +"Black/white mask, white = area to landscape (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"
      -}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, non-idempotent and non-destructive; the description adds genuinely new behavior in its 'Costs 1 credit' disclosure and in noting that the operation is confined to a masked region, which implies non-selected pixels are preserved. It falls short of saying how the output comes back (generated image vs. job requiring luw_get_result), which matters for a non-idempotent generation call.

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?

Two compact sentences with the core action and its scoping constraint front-loaded, and the cost note placed last where it is easy to scan. The leading 'Luw.ai Landscape AI:' prefix largely restates the title and could be trimmed, but nothing else is wasted.

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?

With 6 parameters, full schema coverage, and no output schema, the description covers inputs adequately but leaves the return contract unstated — an agent cannot tell whether it receives an image directly or must poll luw_get_result. Adding one clause about the output and any async behavior would make this complete for a paid generation tool.

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 (city, image, mask_image, prompt, sun_exposure, enhance_prompt) is already documented in the schema and the baseline is 3. The description reinforces the intent behind city and sun_exposure ('plants chosen for the location's climate and sun exposure') but adds no syntax, format, or constraint detail beyond the structured fields.

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: 'design a garden, yard or outdoor area inside a masked region of a photo,' plus the differentiator that plants are chosen for climate and sun exposure. That separates it from interior/repaint siblings, but it never distinguishes it from the closely related luw_exterior_design sibling, which an agent could easily confuse with this one.

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?

Usage is implied by the resource description ('garden, yard or outdoor area') and by the hard requirement that a mask be supplied, and the credit cost is disclosed. However, there is no explicit when-to-use/when-not guidance and no routing to an alternative tool such as luw_exterior_design or luw_sketch_to_render for overlapping outdoor tasks.

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