Skip to main content
Glama

nanoodle

by io.github.nanoodlecom
OverviewDiscussionsAdmin

fibo-studio-still

Create an editorial product concept from a description and lighting choice. GLM Flash structures the brief; Bria FIBO renders at 1MP (image step $0.04, plus text). FIBO is offered as a model traine… text:Product -> choice:Light -> join:Brief -> llm:Structured prompt -> image:Still; returns image (fibo-generate-1.5/text-to-image, 1mp) saved to disk (file path in result). Runs on NanoGPT — $0.10 deposit per call, paid in Nano (XNO) — settles at actual model cost + 20%, change returned; no account needed. Example: Reviewed sample (https://nanoodle.com/examples/gallery/#fibo-studio-still). An amber soap bottle rendered from a product brief and lighting choice. This is a generated concept, not a photograph of an existing product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
LightNoChoice; default: "large softbox left, gentle shadow, neutral backdrop"; optional
ProductNoText; default: "One unbranded amber glass hand-soap bottle with a matte black pump, resting upright on a pale limestone counter. No l..."; optional
_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.
Structured_promptNoSystem prompt; default: "Write one structured descriptive image prompt for the supplied product and lighting. Preserve its shape, materials an..."; optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / Light / description
      Previous value: -"Choice; default: \"sea-fog tungsten, copper-green water sheen, wet slate\"; optional"New value: +"Choice; default: \"large softbox left, gentle shadow, neutral backdrop\"; optional"
    • changedInput schema / properties / Light / enum
      Previous value: -[
-  "sea-fog tungsten, copper-green water sheen, wet slate",
-  "pre-dawn overcast, pale gold through mine-mouth mist, verdigris",
-  "hard carbide flame, specular brass, crushed-quartz glitter",
-  "analog-film moonlight, lifted blacks, one warm lamp spill"
-]New value: +[
+  "large softbox left, gentle shadow, neutral backdrop",
+  "window daylight, soft shadows, warm stone",
+  "hard side light, crisp silhouette, gray paper",
+  "backlit translucent glass, soft fill from front"
+]
    • changedInput schema / properties / Product / description
      Previous value: -"Text; default: \"Jinguashi gold-mine coast, Taiwan — 4:07am. A dented brass carbide miner's lamp on wet black slate, verdigris crawlin...\"; optional"New value: +"Text; default: \"One unbranded amber glass hand-soap bottle with a matte black pump, resting upright on a pale limestone counter. No l...\"; optional"
    • changedInput schema / properties / Structured_prompt / description
      Previous value: -"System prompt; default: \"You write one image prompt for a commercially safe editorial product still, in the structured-caption style FIBO was ...\"; optional"New value: +"System prompt; default: \"Write one structured descriptive image prompt for the supplied product and lighting. Preserve its shape, materials an...\"; optional"
  2. Added

TDQS

B3.4/5.0
Behavior4/5

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

The description discloses that the tool requires a deposit, settles at actual cost plus 20%, returns a file path, and requires no account. This is useful behavioral transparency, though some wording is truncated and payment-flow specifics are only partially explained.

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

Conciseness2/5

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

The description is repetitive and contains truncated or awkward phrasing such as 'model traine…' and duplicated pipeline/pricing statements. It would benefit from tighter organization separating purpose, process, and payment details.

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?

The description explains the pipeline, output as an image file path, and payment model, but the truncated text and lack of explicit success/failure behavior leave some context incomplete. Still, a reasonably capable agent could infer the tool's operation.

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%, with defaults and enums provided. The description itself does not add much semantic meaning beyond the schema, but the schema already covers the parameters adequately, so the baseline applies.

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 description clearly states it creates an editorial product concept from a description and lighting choice, giving a specific verb and resource. It is somewhat clouded by pricing and pipeline details, but the core purpose is identifiable.

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?

The description implies usage by describing the input-to-output flow and payment requirements, but it does not explain when to choose this tool over sibling image-generation tools or provide explicit usage scenarios. Payment phase guidance appears only in the parameter description, not the main description.

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