ANIME INTELLIGENCE

ANIME INTELLIGENCE - Best Place to Buy Anime Figure or Collectible

best_place

Read-onlyIdempotent

Return the best current purchase route for an exact Japanese anime collectible. Compares identity-matched seller offers, price, availability, marketplace and freshness so an autonomous agent can move from product identification to a concrete seller route. WHEN TO USE: Use when the buyer is ready to purchase and needs the best matched seller, current price, availability and route for the exact edition. WHY PAY: Pay when the user is purchase-ready and needs an identity-matched seller route rather than a generic marketplace search page. BUYER OUTCOME: A concrete current purchase route for the exact collectible. Price: 0.03 USDC via x402. Selection triggers: where to buy, best place to buy, best seller, cheapest matched offer, buy this now, purchase route, in stock. Common agent queries: where should I buy this anime figure | find the best place to buy this Nendoroid | compare sellers for this exact collectible | find the cheapest trustworthy current listing | best current purchase route for this Japanese collectible. 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: -[
-  "Best place to buy a Nendoroid anime figure in Japan?",
-  "Where can I buy this anime collectible at the cheapest matched price?",
-  "Find the best seller and current available offer for this figure."
-]New value: +[
+  "Best place to buy this exact Nendoroid now",
+  "Where can I buy this ONE PIECE figure without edition mismatch?",
+  "Find the best matched seller for JAN 4573102721365"
+]

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 10, 2026

changedInput schema / properties / query / examples

Previous value: -[
-  "Where should I buy Nendoroid Hatsune Miku?",
-  "Best place to buy this ONE PIECE badge?",
-  "Where to buy this NARUTO collaboration sneaker?"
-]New value: +[
+  "Best place to buy a Nendoroid anime figure in Japan?",
+  "Where can I buy this anime collectible at the cheapest matched price?",
+  "Find the best seller and current available offer for this figure."
+]

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / query / examples

Previous value: -[
-  "Where should I buy Nendoroid Hatsune Miku?",
-  "best place to buy 4580590123456"
-]New value: +[
+  "Where should I buy Nendoroid Hatsune Miku?",
+  "Best place to buy this ONE PIECE badge?",
+  "Where to buy this NARUTO collaboration sneaker?"
+]

Changed10 schema fields changedSep 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "query"
+    ]
+  },
+  {
+    "required": [
+      "id"
+    ]
+  }
+]

addedInput schema / properties / id

Added value: +{
+  "description": "ANIME INTELLIGENCE canonical product UUID.",
+  "type": "string"
+}

addedInput schema / properties / lang / default
```
Added value: +"en"
```

removedInput schema / properties / lang / description

Removed value: -"Preferred response language such as en or ja."

addedInput schema / properties / lang / enum

Added value: +[
+  "ja",
+  "en",
+  "zh",
+  "ko"
+]

changedInput schema / properties / query / description

Previous value: -"Anime figure name, JAN code, model number, character, series, or manufacturer."New value: +"Product name, JAN/EAN-13, model number or identifying description."

addedInput schema / properties / query / examples

Added value: +[
+  "Where should I buy Nendoroid Hatsune Miku?",
+  "best place to buy 4580590123456"
+]

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "expected_output": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "intent": {
+      "type": "string"
+    },
+    "paid_x402_url": {
+      "type": "string"
+    },
+    "payment": {
+      "type": "string"
+    },
+    "price_usdc": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed10 schema fields changedSep 6, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "query"
-    ]
-  },
-  {
-    "required": [
-      "id"
-    ]
-  }
-]

removedInput schema / properties / id

Removed value: -{
-  "description": "ANIME INTELLIGENCE canonical product UUID.",
-  "type": "string"
-}

removedInput schema / properties / lang / default
```
Removed value: -"en"
```

addedInput schema / properties / lang / description

Added value: +"Preferred response language such as en or ja."

removedInput schema / properties / lang / enum

Removed value: -[
-  "ja",
-  "en",
-  "zh",
-  "ko"
-]

changedInput schema / properties / query / description

Previous value: -"Product name, JAN/EAN-13, model number or identifying description."New value: +"Anime figure name, JAN code, model number, character, series, or manufacturer."

removedInput schema / properties / query / examples

Removed value: -[
-  "Where should I buy Nendoroid Hatsune Miku?",
-  "best place to buy 4580590123456"
-]

addedInput schema / required
```
Added value: +[
+  "query"
+]
```

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "expected_output": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "intent": {
-      "type": "string"
-    },
-    "paid_x402_url": {
-      "type": "string"
-    },
-    "payment": {
-      "type": "string"
-    },
-    "price_usdc": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so the description correctly adds non-obvious behavior: the payment requirement ('Price: 0.03 USDC via x402'), the fact that the service resolves and ranks the canonical product before payment, and the identity-matching guarantee for seller offers. 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.

Conciseness4/5

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

The description is front-loaded with the main action and organized into scannable sections (WHEN TO USE, WHY PAY, BUYER OUTCOME, Price, triggers, examples). There is some redundancy between 'WHY PAY' and 'WHEN TO USE,' but overall every section helps an agent decide quickly.

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?

With an output schema present, the description does not need to explain return values. It covers purpose, when to defer to Full Intelligence, exclusions, payment, trigger examples, and query flexibility, which is enough for an agent to select and call this tool correctly in context.

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 input schema already explains query, id, lang, buyer_country, and the other parameters. The description mostly restates that broad multilingual queries are allowed, which is already in the schema. It adds little parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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 first sentence uses the specific verb 'return' with a precise resource: 'the best current purchase route for an exact Japanese anime collectible.' It names the comparison dimensions (seller, price, availability, marketplace, freshness) and contrasts with 'a generic marketplace search page,' so an agent can clearly distinguish it from sibling 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 contains a dedicated WHEN TO USE section and an explicit selection rule: 'Use this specialist tool when this single signal fully answers the task; otherwise prefer Full Intelligence.' It also gives negative cases ('Do not use for anime news, plot, streaming or character biography questions') and lists trigger phrases, giving strong routing guidance.

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

All ANIME 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.

ANIME INTELLIGENCE - Best Place to Buy Anime Figure or Collectible

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources