nanoodle

image-model-arena

Compare four image models on the same brief. Run makes four paid images. Judge the exact heading and footer, object count, tool shapes, composition and color. Change the shared brief to test your o… text:Shared test brief -> image:Contender 1 -> image:Contender 2 -> image:Contender 3 -> image:Contender 4; returns image (muse-image/text-to-image, 1:1) + image (gpt-image-2.5/flare/text-to-image, 1k) + image (grok-imagine-image/v2.0/text-to-image, 1:1) + image (recraft-v4, 1024×1024) saved to disk (file paths in result). Runs on NanoGPT — $0.40 deposit per call, paid in Nano (XNO) — settles at actual model cost + 20%, change returned; no account needed; last run $0.264, ~73s. Example: Reviewed sample (https://nanoodle.com/examples/gallery/#image-model-arena). The same bicycle-repair poster brief sent to four image models. All four retained the requested text in this run; only Grok rendered recognizable tire levers. Compare all outputs before choosing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "image-model-arena"
  }
}

Input Schema

Name	Required	Description	Default
`_payment_id`	No	Payment 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.
`Shared_test_brief`	No	Text; default: "Create a square poster for a bicycle repair workshop. Exact heading: FIX A FLAT. Exact footer: SATURDAY 10 AM. A sing..."; optional

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / Shared_test_brief

Added value: +{
+  "description": "Text; default: \"Create a square poster for a bicycle repair workshop. Exact heading: FIX A FLAT. Exact footer: SATURDAY 10 AM. A sing...\"; optional",
+  "type": "string"
+}

removedInput schema / properties / Text

Removed value: -{
-  "description": "default: \"Liziba, Chongqing at 11:47pm: Light Rail Line 2 frozen mid-crossing through the 6th–8th floors of a lived-in resident...\"; optional",
-  "type": "string"
-}

Changed1 schema field changedSep 5, 2026

changedInput schema / properties / Text / description

Previous value: -"default: \"a tiny dragon curled up asleep in a teacup, macro photo, soft morning light\"; optional"New value: +"default: \"Liziba, Chongqing at 11:47pm: Light Rail Line 2 frozen mid-crossing through the 6th–8th floors of a lived-in resident...\"; optional"

First observedAug 13, 2026

TDQS

A4.2/5.0

Behavior5/5

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

With no annotations, the description carries the entire burden and does so well: it discloses cost structure ($0.40 deposit, settles at actual model cost + 20%, last run $0.264), payment currency and that no account is needed, expected latency (~73s), that four paid images are generated, and that outputs are saved to disk with file paths in the result.

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 purpose and cost details are front-loaded, but the middle is cluttered with a concatenated model/output chain and a truncated fragment ('test your o…'), which is a structural defect. 'Compare all outputs before choosing' largely restates the opening sentence.

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

Completeness4/5

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

There is no output schema, and the description compensates by specifying each model, aspect ratio, resolution, and that files are written to disk. Pricing, latency, and payment handling are covered, leaving little an agent would need before calling it.

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 coverage is 100%, so the two parameters are already documented, including the _payment_id phase-3 flow. The description only lightly reinforces the shared brief ('Change the shared brief to test your...'), which is the baseline expectation when the schema does the heavy lifting.

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 opening sentence names a specific verb and resource ('Compare four image models on the same brief') and the run/return summary enumerates exactly which four models are invoked. An agent can distinguish this from siblings like storyboard-relay or character-sprites without opening the schema.

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?

It gives clear operating context: change the shared brief to test variants, and 'Compare all outputs before choosing' tells the agent what to do with the result. It stops short of naming when NOT to use it or an explicit alternative tool, so it is not a full 5.

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

All nanoodle tools Inspect

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.