ANIME INTELLIGENCE / AI PURCHASE INTELLIGENCE

ANIME INTELLIGENCE - Buy or Wait Decision for Anime Collectibles

anime_buy_wait

Read-onlyIdempotent

Turn Japanese collectible data into an actionable BUY, WAIT, WATCH or AVOID decision. Uses identity-matched price, availability, scarcity, rerelease/replenishment risk and authenticity signals so an agent can act instead of assembling several searches manually. WHEN TO USE: Use when an autonomous shopping agent must decide whether to buy now rather than merely report data. Especially useful when waiting for a rerelease or avoiding a scarcity premium could save money. WHY PAY: Pay when the agent must make a timing decision. This converts price, scarcity, rerelease and risk signals into a direct action instead of returning raw data. BUYER OUTCOME: A BUY, WAIT, WATCH or AVOID decision with reasons. Price: 0.02 USDC via x402. Selection triggers: buy now, buy or wait, should I buy, wait for rerelease, watch, avoid, purchase timing, is now a good time. Common agent queries: should I buy this anime figure now | buy or wait for this Nendoroid | should I wait for a rerelease | is now a good time to buy this collectible | BUY WAIT WATCH or AVOID this figure. Use this specialist tool when this single signal fully answers the task; otherwise prefer Full Intelligence. Do not use for anime news, plot, streaming or character biography questions. Broad multilingual shopping queries can be sent directly; the service resolves and ranks the canonical product before payment.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	ANIME INTELLIGENCE canonical product UUID. Use for deterministic exact-product calls when already known.
`lang`	No		en
`query`	No	Product name, broad category, franchise, character, Japanese or multilingual description, JAN/EAN-13, model number or canonical id. Broad shopping queries are allowed and auto-ranked before x402.
`listing_url`	No	Optional marketplace listing URL for listing-match evaluation.
`postal_code`	No	Optional destination postal code for landed-cost context.
`buyer_country`	No	ISO 3166-1 alpha-2 buyer destination. Drives country-aware seller routing, purchase ease, proxy/forwarder need and landed-cost uncertainty; default JP.	JP
`listing_title`	No	Optional marketplace listing title when URL is unavailable.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`intent`	No
`payment`	No
`why_pay`	No
`price_usdc`	No
`buyer_outcome`	No
`paid_x402_url`	No
`expected_output`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedInput schema / properties / buyer_country / description

Previous value: -"ISO 3166-1 alpha-2 buyer destination. JP is fully supported as a first-class domestic-buyer case; default JP."New value: +"ISO 3166-1 alpha-2 buyer destination. Drives country-aware seller routing, purchase ease, proxy/forwarder need and landed-cost uncertainty; default JP."

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / lang / enum

Previous value: -[
-  "ja",
-  "en",
-  "zh",
-  "ko",
-  "es",
-  "fr",
-  "de",
-  "it",
-  "pt",
-  "id",
-  "th",
-  "ru",
-  "ar",
-  "hi",
-  "vi",
-  "tr",
-  "nl",
-  "pl"
-]New value: +[
+  "ja",
+  "en",
+  "zh",
+  "ko",
+  "es",
+  "fr",
+  "de"
+]

Changed4 schema fields changedSep 16, 2026

addedInput schema / properties / buyer_country

Added value: +{
+  "default": "JP",
+  "description": "ISO 3166-1 alpha-2 buyer destination. JP is fully supported as a first-class domestic-buyer case; default JP.",
+  "type": "string"
+}

addedInput schema / properties / listing_title

Added value: +{
+  "description": "Optional marketplace listing title when URL is unavailable.",
+  "type": "string"
+}

addedInput schema / properties / listing_url

Added value: +{
+  "description": "Optional marketplace listing URL for listing-match evaluation.",
+  "type": "string"
+}

addedInput schema / properties / postal_code

Added value: +{
+  "description": "Optional destination postal code for landed-cost context.",
+  "type": "string"
+}

Changed3 schema fields changedSep 14, 2026

changedInput schema / properties / id / description

Previous value: -"ANIME INTELLIGENCE canonical product UUID."New value: +"ANIME INTELLIGENCE canonical product UUID. Use for deterministic exact-product calls when already known."

addedOutput schema / properties / buyer_outcome

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / why_pay
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedSep 14, 2026

changedInput schema / properties / query / description

Previous value: -"Exact product name, JAN/EAN-13 or model number. For broad requests use search_anime_product first and pass its canonical id."New value: +"Product name, broad category, franchise, character, Japanese or multilingual description, JAN/EAN-13, model number or canonical id. Broad shopping queries are allowed and auto-ranked before x402."

changedInput schema / properties / query / examples

Previous value: -[
-  "Should I buy this Nendoroid now?",
-  "Buy or wait for this ONE PIECE lottery prize?",
-  "Should I buy this anime collaboration sneaker now?"
-]New value: +[
+  "Buy or wait for this ONE PIECE figure?",
+  "Should I buy this Nendoroid now or wait for rerelease?",
+  "BUY WAIT WATCH or AVOID this Japanese collectible"
+]

Changed1 schema field changedSep 13, 2026

changedInput schema / properties / query / description

Previous value: -"Product name, JAN/EAN-13, model number or identifying description."New value: +"Exact product name, JAN/EAN-13 or model number. For broad requests use search_anime_product first and pass its canonical id."

Changed1 schema field changedSep 12, 2026

changedInput schema / properties / lang / enum

Previous value: -[
-  "ja",
-  "en",
-  "zh",
-  "ko"
-]New value: +[
+  "ja",
+  "en",
+  "zh",
+  "ko",
+  "es",
+  "fr",
+  "de",
+  "it",
+  "pt",
+  "id",
+  "th",
+  "ru",
+  "ar",
+  "hi",
+  "vi",
+  "tr",
+  "nl",
+  "pl"
+]

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / query / examples

Previous value: -[
-  "Should I buy this Nendoroid now?",
-  "buy or wait for this limited figure"
-]New value: +[
+  "Should I buy this Nendoroid now?",
+  "Buy or wait for this ONE PIECE lottery prize?",
+  "Should I buy this anime collaboration sneaker now?"
+]

AddedSep 6, 2026
RemovedSep 6, 2026
First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already indicate a safe read-only, idempotent operation, and the description adds useful extra context: a 0.02 USDC x402 payment, pre-payment canonical product resolution, and the fact that it produces a decision rather than executing a purchase. No contradiction with annotations.

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 heavily redundant: WHEN TO USE and WHY PAY cover similar ground, and Selection triggers largely duplicates Common agent queries. While the headings make it skimmable, several sentences repeat the same point and the description is longer than necessary.

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?

Given the output schema, input schema, and annotations, the description covers the key decision context an agent needs: when to pay, what decision outcome to expect, example queries, product resolution behavior, and when to defer to Full Intelligence. Nothing critical for tool selection is missing.

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 86% and the query parameter already documents product names, categories, JAN/EAN-13, model numbers, multilingual input, and auto-ranking before x402. The description largely restates this information, so it adds little beyond the schema's already-rich parameter documentation.

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 states a specific decision output — BUY, WAIT, WATCH, or AVOID — from Japanese collectible data, and explicitly contrasts itself with raw-data reporting and Full Intelligence. This makes it clearly distinguishable from its sibling specialist tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes an explicit WHEN TO USE section, example trigger phrases and queries, a clear exclusion ('Do not use for anime news, plot, streaming or character biography'), and names Full Intelligence as the alternative when this single signal is insufficient.

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

All ANIME INTELLIGENCE / AI PURCHASE INTELLIGENCE 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.