Skip to main content
Glama

nanoodle

by io.github.nanoodlecom
OverviewDiscussionsAdmin

photo-to-video

Make a five-second ambient loop concept: Muse draws the first frame ($0.01), MiniMax H3 Spicy animates one small movement (480p, $0.20). This model supports image-to-video; the scene is a simple pr… text:Still brief -> text:Motion brief -> image:First frame -> ivideo:Animated clip; returns video (image-to-video-spicy) saved to disk (file path in result). Runs on NanoGPT — $0.51 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/#photo-to-video). A short tea-on-a-desk animation. Sampled frames retained the mug while steam moved. This thumbnail is one frame; the example does not establish a seamless loop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
Still_briefNoText; default: "A ceramic mug of hot tea on an oak desk beside a closed notebook. Soft morning window light from the left, plain warm..."; 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.
Motion_briefNoText; default: "Locked camera for five seconds. A thin wisp of steam rises slowly from the tea and curls gently in the window light. ..."; optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / Motion_brief
      Added value: +{
+  "description": "Text; default: \"Locked camera for five seconds. A thin wisp of steam rises slowly from the tea and curls gently in the window light. ...\"; optional",
+  "type": "string"
+}
    • addedInput schema / properties / Still_brief
      Added value: +{
+  "description": "Text; default: \"A ceramic mug of hot tea on an oak desk beside a closed notebook. Soft morning window light from the left, plain warm...\"; optional",
+  "type": "string"
+}
    • removedInput schema / properties / motion_system_prompt
      Removed value: -{
-  "description": "Text; default: \"You are writing a motion prompt for MiniMax H3 Spicy image-to-video.\\nPrompting guide:\\n1. Be specific. Name subjects, ...\"; optional",
-  "type": "string"
-}
    • removedInput schema / properties / movement
      Removed value: -{
-  "description": "Text; default: \"she takes one careful step down the fire-escape grate, red silk billows sideways in a wet gust, camera slow orbit rig...\"; optional",
-  "type": "string"
-}
    • removedInput schema / properties / the_image_being
      Removed value: -{
-  "description": "Text; default: \"photoreal fashion editorial, adult woman STANDING upright full-body three-quarter view on a wet Tokyo fire-escape lan...\"; optional",
-  "type": "string"
-}
  2. Changed3 schema fields changed
    • changedInput schema / properties / motion_system_prompt / description
      Previous value: -"Text; default: \"You are animating this image for ltx-2.3.\\nPromptig guide:\\n1. Be More Specific. The Engine Can Handle It.\\nLTX-2.3 incl...\"; optional"New value: +"Text; default: \"You are writing a motion prompt for MiniMax H3 Spicy image-to-video.\\nPrompting guide:\\n1. Be specific. Name subjects, ...\"; optional"
    • changedInput schema / properties / movement / description
      Previous value: -"Text; default: \"sailing very fast in rough seas\"; optional"New value: +"Text; default: \"she takes one careful step down the fire-escape grate, red silk billows sideways in a wet gust, camera slow orbit rig...\"; optional"
    • changedInput schema / properties / the_image_being / description
      Previous value: -"Text; default: \"a tiny sailboat on a glowing bioluminescent sea, night, stars\"; optional"New value: +"Text; default: \"photoreal fashion editorial, adult woman STANDING upright full-body three-quarter view on a wet Tokyo fire-escape lan...\"; optional"
  3. First observed

TDQS

A3.9/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 transparently discloses the payment model ($0.51 deposit in Nano, 20% fee), the two-step generation (Muse draws frame, MiniMax animates), and that it returns a video saved to disk. It does not mention destructive actions, but no such side effects are implied.

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

Conciseness3/5

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

The description is somewhat rambling, mixing cost details, pipeline explanation, and an example in a single sentence with typos (e.g., 'NanoGPT' vs 'Nano'). It could be more concise and better structured, but it is still readable.

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?

No output schema is provided, but the description states the result is a video file saved to disk with a file path returned. It does not specify video format, resolution beyond 480p, or any error responses, which would be helpful for full context.

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?

The schema describes Still_brief and Motion_brief with defaults and _payment_id with detailed phase instructions. The tool description adds context by explaining the pipeline (Still brief -> Motion brief -> image -> video), clarifying the role of each text parameter beyond the schema.

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 generates a five-second ambient video loop from a still image, describing the image-to-video pipeline (text briefs -> first frame -> animated clip). This distinguishes it from sibling tools that produce static images or other media.

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 explains the tool's function and workflow but does not explicitly state when to prefer it over siblings (e.g., 'use this instead of fibo-studio-still when you need motion'). The example and cost details hint at usage, but no direct guidance is given.

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