Skip to main content
Glama

nanoodle

by io.github.nanoodlecom
OverviewDiscussionsAdmin

omni-flash-turntable

Create a short product-motion concept from an object and camera move. GLM Flash structures the brief; Omni Flash 1.1 renders 5s at 360p / 16:9 (video step $0.195, plus text). No upload required. In… text:Object -> choice:Move -> join:Brief -> llm:Video prompt -> tvideo:Clip; returns video (gemini-omni-flash/v1.1) 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/#omni-flash-turntable). A 360p draft camera orbit around a generated bottle with coherent geometry in the reviewed clip. This thumbnail is one frame; open the sample to inspect the motion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
MoveNoChoice; default: "camera makes a slow quarter-orbit; object stays still"; optional
ObjectNoText; default: "One unbranded matte sage-green insulated water bottle with a black screw cap on a stationary pale-gray studio plinth,..."; 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.
Video_promptNoSystem prompt; default: "Write one text-to-video prompt from the object brief and selected move. Preserve the object, material, color, setting..."; optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / Move / description
      Previous value: -"Choice; default: \"slow clockwise orbit through dock fog, tungsten key left, salt spray, wet teak grain\"; optional"New value: +"Choice; default: \"camera makes a slow quarter-orbit; object stays still\"; optional"
    • changedInput schema / properties / Move / enum
      Previous value: -[
-  "slow clockwise orbit through dock fog, tungsten key left, salt spray, wet teak grain",
-  "lazy quarter-turn, north-window daylight, linen behind",
-  "locked-off, seawater sheets down the visor as it rotates, specular rivets, tungsten",
-  "push-in while it rotates, overcast skylight, fog rolling, teak grain sharp"
-]New value: +[
+  "camera makes a slow quarter-orbit; object stays still",
+  "locked camera; object rotates slowly clockwise",
+  "slow camera push-in; object stays still"
+]
    • changedInput schema / properties / Object / description
      Previous value: -"Text; default: \"Barnacled brass diving helmet on a rain-slick teak ship's binnacle, visor fogged from inside, no labels or brand mark...\"; optional"New value: +"Text; default: \"One unbranded matte sage-green insulated water bottle with a black screw cap on a stationary pale-gray studio plinth,...\"; optional"
    • changedInput schema / properties / Video_prompt / description
      Previous value: -"System prompt; default: \"You write one text-to-video prompt for Gemini Omni Flash 1.1. Combine the object and the move into a single cinematic...\"; optional"New value: +"System prompt; default: \"Write one text-to-video prompt from the object brief and selected move. Preserve the object, material, color, setting...\"; optional"
  2. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses costs, payment mechanics, that no upload is required, and that the output is saved to disk. No destructive actions are implied and there are no contradictions.

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 cluttered with extraneous pricing details, a garbled pipeline string, an example URL, and an odd 'thumbnail is one frame' note. This makes it harder to parse the essential information quickly.

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 covers cost, output, defaults, and payment flow, but no output schema exists and the narrative is muddled by promotional and example content. It is adequate but not fully polished.

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%, with each parameter described. Most descriptions are redundant with the schema, but _payment_id adds significant workflow context about phases and when to pass it. This extra detail lifts the score above baseline.

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?

The description clearly states the tool creates a short product-motion concept from an object and camera move, and mentions the output is a video saved to disk. This is specific enough to distinguish it from sibling tools like photo-to-video or render-a-mockup.

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?

The description provides usage hints like 'No upload required' and explains the payment flow via _payment_id in the schema. It does not explicitly name alternatives, but the purpose and conditions are reasonably clear.

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