Skip to main content
Glama

nanoodle

by io.github.nanoodlecom
OverviewDiscussionsAdmin

talking-avatar

Prototype a short spoken introduction with a fictional presenter. Muse makes the portrait, MiniMax Speech reads the script, and LongCat animates speech at 480p. Keep scripts under 30 seconds. Cost … text:Presenter look -> text:Spoken script -> text:Delivery -> image:face -> tts -> lipsync; returns video (longcat-avatar-1.5) saved to disk (file path in result). Runs on NanoGPT — $0.53 deposit per call, paid in Nano (XNO) — settles at actual model cost + 20%, change returned; no account needed. Example: Video sample (https://nanoodle.com/examples/gallery/#talking-avatar). A fictional presenter reads a short workshop introduction. Sampled frames preserve the presenter; check precise lip-sync timing in playback. Generation can take several minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
DeliveryNoText; default: "Natural calm delivery, subtle blinks and small head movements. Keep the face and mouth visible, eyes toward the camer..."; 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.
Spoken_scriptNoText; default: "Welcome to the workshop. Start with the blue tray on your table. Inside you will find paper, a pencil, and the parts ..."; optional
Presenter_lookNoText; default: "A fictional friendly male museum guide in his thirties, wearing a plain navy shirt, shoulders-up front-facing portrai..."; optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / Delivery
      Added value: +{
+  "description": "Text; default: \"Natural calm delivery, subtle blinks and small head movements. Keep the face and mouth visible, eyes toward the camer...\"; optional",
+  "type": "string"
+}
    • addedInput schema / properties / Presenter_look
      Added value: +{
+  "description": "Text; default: \"A fictional friendly male museum guide in his thirties, wearing a plain navy shirt, shoulders-up front-facing portrai...\"; optional",
+  "type": "string"
+}
    • addedInput schema / properties / Spoken_script
      Added value: +{
+  "description": "Text; default: \"Welcome to the workshop. Start with the blue tray on your table. Inside you will find paper, a pencil, and the parts ...\"; optional",
+  "type": "string"
+}
    • removedInput schema / properties / look
      Removed value: -{
-  "description": "Text; default: \"cinematic film still of a night courier, late 20s, on the cliff-walk at Hongyadong, Chongqing, 2:11am: cropped black ...\"; optional",
-  "type": "string"
-}
    • removedInput schema / properties / movement
      Removed value: -{
-  "description": "Text; default: \"Natural talking-head: small nods timed to the speech, Hongyadong lantern-light catching the visor, slight jaw set, st...\"; optional",
-  "type": "string"
-}
    • removedInput schema / properties / speak
      Removed value: -{
-  "description": "Text; default: \"Last drop of the night. Hongyadong, cliff side. If the stairs flood, tell dispatch I climbed it — the package is alre...\"; optional",
-  "type": "string"
-}
  2. Changed5 schema fields changed
    • removedInput schema / properties / Image
      Removed value: -{
-  "description": "* required; image — file path or https URL",
-  "type": "string"
-}
    • addedInput schema / properties / look
      Added value: +{
+  "description": "Text; default: \"cinematic film still of a night courier, late 20s, on the cliff-walk at Hongyadong, Chongqing, 2:11am: cropped black ...\"; optional",
+  "type": "string"
+}
    • changedInput schema / properties / movement / description
      Previous value: -"Text; default: \"exaggerated head movement\"; optional"New value: +"Text; default: \"Natural talking-head: small nods timed to the speech, Hongyadong lantern-light catching the visor, slight jaw set, st...\"; optional"
    • changedInput schema / properties / speak / description
      Previous value: -"Text; default: \"Hi there! I used to be a still photo — then somebody wired three nodes together, and now I won't stop talking.\"; optional"New value: +"Text; default: \"Last drop of the night. Hongyadong, cliff side. If the stairs flood, tell dispatch I climbed it — the package is alre...\"; optional"
    • removedInput schema / required
      Removed value: -[
-  "Image"
-]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full disclosure burden and delivers: the payment model ('$0.53 deposit per call, paid in Nano (XNO) — settles at actual model cost + 20%, change returned'), output behavior ('returns video (longcat-avatar-1.5) saved to disk (file path in result)'), runtime ('Generation can take several minutes'), and a caveat ('check precise lip-sync timing in playback'). This is exemplary behavioral disclosure well beyond what the schema provides.

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 dense and mostly earns its length, but the 'Cost … text:Presenter look -> …' transition is structurally broken — it reads as a truncated sentence that awkwardly merges the cost topic with the pipeline diagram. The example section ('Example: Video sample (URL). A fictional presenter reads…') is slightly disorganized, and the opening purpose partially duplicates the Presenter_look default. Front-loading of purpose is good, but the flow needs polish.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool — 4 optional params, a payment-required two-phase flow, multi-minute generation, and no output schema — the description covers what matters: the produced artifact (video file saved to disk, path in result), generation time, cost and settlement mechanics, and the lip-sync caveat. The only flow detail left to the schema is the _payment_id watch/stream protocol, which the schema documents thoroughly. Nothing an agent needs to call this successfully is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning by mapping params to pipeline stages ('text:Presenter look -> text:Spoken script -> text:Delivery -> image:face -> tts -> lipsync') and by constraining the Spoken_script param ('Keep scripts under 30 seconds') — a constraint the schema does not express. The _payment_id flow is already thoroughly documented in the schema, so no compensation is needed there.

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?

Opens with a specific verb+resource: 'Prototype a short spoken introduction with a fictional presenter.' The pipeline detail (Muse makes the portrait, MiniMax Speech reads the script, LongCat animates speech at 480p) makes the function unmistakable and inherently distinguishes it from siblings like 'sing' (singing) and 'photo-to-video' (photo animation). An agent cannot confuse this with a sprite generator, image editor, or mockup renderer.

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?

Provides clear usage context: it is for prototyping short spoken introductions, with an explicit constraint ('Keep scripts under 30 seconds'), an example use case ('A fictional presenter reads a short workshop introduction'), and expectations for cost and runtime ('no account needed', 'Generation can take several minutes'). It does not name explicit alternatives or when-not-to-use conditions, which keeps it from a 5.

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