Skip to main content
Glama
Sign In

Luw.ai

by ai.luw
OverviewDiscussionsAdmin

Edit image with a prompt (Magic Prompt AI)

luw_edit_image

Luw.ai Magic Prompt AI: edit any image with a plain-language instruction: "make the sofa green velvet", "add a pendant lamp over the table", "turn it into a night scene". Pass products, materials or a mood board as reference_images to place or apply them. For edits restricted to an exact area, use luw_magic_wand. 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": {
      "prompt": "<prompt>"
    },
    "name": "luw_edit_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoFix for reproducible results.
imageNoImage to edit (https:// URL, local file path, or data: URI).
engineNoModel: aria (default), symphony (Symphony-3) or nano-banana-2.
formatNoOutput image format.
promptYesThe edit to make.
image_fileNoA photo the user attached in the chat. Use it instead of image when the photo was uploaded rather than linked.
resolutionNoOutput resolution (default 2k).
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.
reference_imagesNoUp to 6 reference images (furniture, materials, products, mood boards) to draw from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / image_file
      Added value: +{
+  "description": "A photo the user attached in the chat. Use it instead of image when the photo was uploaded rather than linked.",
+  "properties": {
+    "download_url": {
+      "type": "string"
+    },
+    "file_id": {
+      "type": "string"
+    },
+    "file_name": {
+      "type": "string"
+    },
+    "mime_type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url",
+    "file_id"
+  ],
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "image",
-  "prompt"
-]New value: +[
+  "prompt"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description needn't re-explain mutation. It adds genuinely useful non-annotation context: billing ('Costs 1 credit per variation'), which helps an agent reason about cost when choosing the variations parameter. It does not cover permissions or auth, hence not a 5.

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?

Front-loaded with the purpose, then examples, then the alternative, then cost — a logical priority order. Every sentence carries information and there is no filler.

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?

For a 10-parameter, nested-object tool the description covers purpose, routing, reference-image usage, and cost, while the schema documents all parameters. With no output schema, it could briefly note what is returned (edited image variants), but the omission is minor given the tool's obvious output modality.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema for reference_images ('place or apply them'), clarifying the intended semantics that the schema only vaguely captures as 'to draw from'. It does not, however, clarify the interplay between image and image_file or the engine choices.

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 (edit any image) and the input modality (plain-language instruction), reinforced by three concrete prompt examples. It also names the sibling it is not (luw_magic_wand) for area-restricted edits, so an agent can distinguish it from neighbors without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool (prompt-driven whole-image edits), when to use the alternative (luw_magic_wand for edits restricted to an exact area), and how to use reference_images (pass products/materials/mood boards to place or apply them). Nothing is left to inference.

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

All Luw.ai toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources