Skip to main content
Glama

nanoodle

by io.github.nanoodlecom
OverviewDiscussionsAdmin

combine-images

Upload a product, then a setting, to preview placement before a photoshoot. Muse Edit uses both reference images ($0.01/image). Inspect product identity, scale and contact shadows; this is a concep… upload:Product photo -> upload:Setting photo -> text:Placement brief -> edit:Product in setting; returns image (muse-image/edit) saved to disk (file path in result). Runs on NanoGPT — $0.18 deposit per call, paid in Nano (XNO) — settles at actual model cost + 20%, change returned; no account needed; last run $0.075, ~1m 49s. Example: Reviewed sample (https://nanoodle.com/examples/gallery/#combine-images). A bottle and a mug-on-desk source image combined into one plausible scene. The sample includes both inputs; exact product fidelity needs a separate comparison.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_payment_idNoPayment id from this tool's previous payment-required response. Phase 3 only: after /x402/watch closes with status paid, call again with the same arguments plus this id to open the RESULTS stream. Do not pass it while payment is still pending — monitor the watch SSE first.
Product_photoYes* required; image — file path or https URL
Setting_photoYes* required; image — file path or https URL
Placement_briefNoText; default: "Place the product from image 1 naturally into the setting from image 2. Preserve the product shape, proportions, mate..."; optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / Image
      Removed value: -{
-  "description": "* required; image — file path or https URL",
-  "type": "string"
-}
    • removedInput schema / properties / Image_2
      Removed value: -{
-  "description": "* required; image — file path or https URL",
-  "type": "string"
-}
    • addedInput schema / properties / Placement_brief
      Added value: +{
+  "description": "Text; default: \"Place the product from image 1 naturally into the setting from image 2. Preserve the product shape, proportions, mate...\"; optional",
+  "type": "string"
+}
    • addedInput schema / properties / Product_photo
      Added value: +{
+  "description": "* required; image — file path or https URL",
+  "type": "string"
+}
    • addedInput schema / properties / Setting_photo
      Added value: +{
+  "description": "* required; image — file path or https URL",
+  "type": "string"
+}
    • removedInput schema / properties / Text
      Removed value: -{
-  "description": "default: \"Composite these two people as rival cartographers knee-deep in the flooded sub-basement of the Vatican Secret Archive...\"; optional",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "Image",
-  "Image_2"
-]New value: +[
+  "Product_photo",
+  "Setting_photo"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / Text / description
      Previous value: -"default: \"Make these two people explore a dungeon together\"; optional"New value: +"default: \"Composite these two people as rival cartographers knee-deep in the flooded sub-basement of the Vatican Secret Archive...\"; optional"
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations are absent, so the description carries the burden. It does disclose that the tool 'returns image (muse-image/edit) saved to disk (file path in result)' and references a payment flow, but it does not fully explain side effects, persistence, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely cluttered with irrelevant details including pricing, deposit fees, last run cost, and an example URL. This makes it difficult to parse and detracts from the essential information.

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?

Given the lack of an output schema, the description provides some crucial context (returns a file path, payment flow). However, the information is buried in noise and not organized, making it less accessible than it should be.

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?

The schema already describes all parameters with 100% coverage. The description adds some context about the workflow (upload product, setting, brief) but does not significantly enhance understanding beyond the schema.

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?

The core purpose is clear: 'Upload a product, then a setting, to preview placement before a photoshoot.' This states a specific action and resource. However, the description is cluttered with pricing and example details that dilute the clarity.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. It mentions a use case (preview placement before a photoshoot) but does not compare with sibling tools or specify exclusion criteria.

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

All nanoodle 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