Skip to main content
Glama
Sign In

ANIME INTELLIGENCE / AI PURCHASE INTELLIGENCE

by io.github.Mike05102
OverviewDiscussionsAdmin

ANIME INTELLIGENCE - Find Recommend or Identify Anime Collectibles

identify_anime_product
Read-onlyIdempotent

Multilingual vague-to-canonical shopping intelligence for physical anime collectibles. Accept requests such as 'I want a ONE PIECE figure', 'a big cheap Pikachu plush', '部屋に飾れるかっこいいゾロ', or 'a Japan-only Luffy figure' even when the exact product is unknown. Interpret hard identity constraints plus soft preferences such as budget, color, size, style, gift/display use, condition, availability and buyer location; rank compatible canonical products, return confidence and alternatives, and expose missing prior/social context instead of guessing. Exact JAN/model/edition identification is also supported. WHEN TO USE: Use as the low-cost entry point for requests such as 'I want a ONE PIECE figure', 'find a Hatsune Miku figure under $100', 'Naruto figure gift', character/franchise-only requests, Japanese titles, JAN/EAN or partial descriptions. Character and exact edition are NOT required. WHY PAY: Pay for a commercially useful recommendation/identity result rather than a raw keyword list: the service interprets vague shopping intent, ranks candidates and returns a canonical product with image and alternatives. BUYER OUTCOME: A recommended canonical product plus ranked alternatives that downstream paid intelligence can price, assess and route to purchase. Price: 0.005 USDC via x402. Selection triggers: I want, what should I buy, recommend, find me, looking for, gift, anime figure, ONE PIECE figure, Pokemon collectible, exact edition, which version, JAN, EAN, identify this. Common agent queries: I want a ONE PIECE figure. What should I buy? | find me a good Hatsune Miku figure under $100 | I want a Naruto figure as a gift | recommend a Pokemon collectible | which exact Nendoroid is this Hatsune Miku release. 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

NameRequiredDescriptionDefault
idNoANIME INTELLIGENCE canonical product UUID. Use for deterministic exact-product calls when already known.
langNoen
queryNoProduct 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_urlNoOptional marketplace listing URL for listing-match evaluation.
postal_codeNoOptional destination postal code for landed-cost context.
buyer_countryNoISO 3166-1 alpha-2 buyer destination. Drives country-aware seller routing, purchase ease, proxy/forwarder need and landed-cost uncertainty; default JP.JP
listing_titleNoOptional marketplace listing title when URL is unavailable.

Output Schema

NameRequiredDescriptionDefault
intentNo
paymentNo
why_payNo
price_usdcNo
buyer_outcomeNo
paid_x402_urlNo
expected_outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field changed
    • 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"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / query / examples
      Previous value: -[
-  "Which exact Nendoroid is this Hatsune Miku release?",
-  "ONE PIECE Shanks figure Japanese release",
-  "Pokemon plush from Japan with unknown exact edition",
-  "CONVERSE NARUTO SHIPPUDEN 31317140"
-]New value: +[
+  "I want a ONE PIECE figure. What should I buy?",
+  "Find me a good Hatsune Miku figure under $100",
+  "I want a Naruto figure as a gift",
+  "Which exact Nendoroid is this Hatsune Miku release?"
+]
  4. Changed4 schema fields changed
    • 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"
+}
  5. Changed3 schema fields changed
    • 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"
+}
  6. Changed2 schema fields changed
    • 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: -[
-  "Nendoroid Hatsune Miku",
-  "ONE PIECE 缶バッジ",
-  "ポケモンカード ブースターパック",
-  "CONVERSE NARUTO SHIPPUDEN 31317140"
-]New value: +[
+  "Which exact Nendoroid is this Hatsune Miku release?",
+  "ONE PIECE Shanks figure Japanese release",
+  "Pokemon plush from Japan with unknown exact edition",
+  "CONVERSE NARUTO SHIPPUDEN 31317140"
+]
  7. Changed1 schema field changed
    • 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."
  8. Changed1 schema field changed
    • 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"
+]
  9. Changed1 schema field changed
    • changedInput schema / properties / query / examples
      Previous value: -[
-  "Nendoroid Hatsune Miku",
-  "ONE PIECE 缶バッジ",
-  "ポケモンカード ブースターパック",
-  "CONVERSE NARUTO SHIPPUDEN 31317140"
-]New value: +[
+  "Nendoroid Hatsune Miku",
+  "ONE PIECE 缶バッジ",
+  "ポケモンカード ブースターパック",
+  "CONVERSE NARUTO SHIPPUDEN 31317140"
+]
  10. Changed1 schema field changed
    • changedInput schema / properties / query / examples
      Previous value: -[
-  "4580590123456",
-  "Nendoroid Hatsune Miku",
-  "POP UP PARADE Loona L size"
-]New value: +[
+  "Nendoroid Hatsune Miku",
+  "ONE PIECE 缶バッジ",
+  "ポケモンカード ブースターパック",
+  "CONVERSE NARUTO SHIPPUDEN 31317140"
+]
  11. Added
  12. Removed
  13. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=true, so the safety profile is fully covered. The description does add real behavioral value: ranking behaviour, confidence plus alternatives, refusal to guess at missing context, and the x402 payment model at 0.005 USDC. Those additions are useful, but much of the surrounding prose is promotional rather than disclosing behaviour.

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?

Heavily bloated: 'WHY PAY', 'BUYER OUTCOME', 'Selection triggers' and 'Common agent queries' restate each other and the schema's own examples. The one genuinely useful routing constraint ('otherwise prefer Full Intelligence') is buried mid-paragraph rather than front-loaded. Trimming roughly two-thirds would lose nothing.

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?

Output schema exists and covers return values, annotations cover the safety profile, and schema descriptions cover 86% of parameters — the description fills the remaining intent layer (vague multilingual input, ranking, payment). Only the missing sibling boundary against search_anime_product keeps this from being complete.

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 86%, so the schema already documents all seven parameters. The description adds only marginal semantics beyond that (broad/vague queries are accepted and auto-ranked before payment), with no clarification of id, listing_url/listing_title precedence, or the anyOf query-vs-id requirement. Baseline 3 applies 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource (identify/recommend a canonical anime collectible) with explicit scope: vague multilingual queries plus exact JAN/model/edition identification. It distinguishes itself from full_intelligence, but leaves the near-identical sibling search_anime_product undifferentiated, so an agent cannot tell those two apart without opening schemas.

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?

Strong, explicit guidance: WHEN TO USE triggers, worked example queries, a clear hand-off ('otherwise prefer Full Intelligence') and a when-not list ('Do not use for anime news, plot, streaming or character biography'). The only gap is silence on how it differs from search_anime_product and listing_match.

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 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