Skip to main content
Glama

ANIME INTELLIGENCE / AI PURCHASE INTELLIGENCE

by io.github.Mike05102
OverviewDiscussionsAdmin

ANIME INTELLIGENCE - Anime Figure Market Value & Price Comparison

anime_market
Read-onlyIdempotent

Identity-matched market intelligence for Japanese anime collectibles. Resolve the exact product first, then compare supported Japan and global marketplace observations while rejecting likely wrong editions and name collisions. Returns low/median/high asking prices, offer count, freshness and best matched listing. WHEN TO USE: Use when an agent needs current value, resale context or matched asking prices for a Japanese anime collectible and identity mismatch would make generic marketplace search unreliable. WHY PAY: Pay for identity-matched pricing when generic marketplace search risks mixing rereleases, sizes, prize versions or similarly named goods. BUYER OUTCOME: A matched current valuation and market snapshot for the exact collectible. Price: 0.01 USDC via x402. Selection triggers: current price, market value, worth, resale value, Japan price, global price, price comparison, how much is this worth. Common agent queries: how much is this anime figure worth | what is the current market value of this Nendoroid | compare Japan and global prices for this anime collectible | what is the resale value of this figure | find the current price of this exact 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
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

TableJSON 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. 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"
+}
  4. 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"
+}
  5. 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 一番くじ A賞",
-  "CONVERSE NARUTO SHIPPUDEN 31317140"
-]New value: +[
+  "Current Japan and global market value for this exact ONE PIECE figure",
+  "Price this Nendoroid without mixing rereleases",
+  "Compare matched asking prices for JAN 4573102721365"
+]
  6. 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."
  7. 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"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / query / examples
      Previous value: -[
-  "Nendoroid Hatsune Miku",
-  "ONE PIECE 一番くじ A賞",
-  "CONVERSE NARUTO SHIPPUDEN 31317140"
-]New value: +[
+  "Nendoroid Hatsune Miku",
+  "ONE PIECE 一番くじ A賞",
+  "CONVERSE NARUTO SHIPPUDEN 31317140"
+]
  9. Changed1 schema field changed
    • changedInput schema / properties / query / examples
      Previous value: -[
-  "Good Smile Hatsune Miku Nendoroid",
-  "4580590123456"
-]New value: +[
+  "Nendoroid Hatsune Miku",
+  "ONE PIECE 一番くじ A賞",
+  "CONVERSE NARUTO SHIPPUDEN 31317140"
+]
  10. Added
  11. Removed
  12. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the bar is lower. The description adds useful behavioral context: it resolves and ranks the canonical product before payment, accepts broad multilingual queries, and rejects mismatched editions. It does not disclose failure modes or payment side effects, but the added context goes beyond the annotations.

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 well-structured with WHEN TO USE, WHY PAY, BUYER OUTCOME, and selection triggers, and it front-loads the core purpose. However, it is considerably longer than needed and contains redundancy: the WHY PAY and BUYER OUTCOME sections repeat the identity-mismatch and valuation points already made in the opening paragraph.

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, paid, identity-matched lookup with an output schema present, the description is complete: it covers purpose, invocation style, query language flexibility, exclusions, alternatives, pricing, and supported marketplaces. An agent has enough information to decide when to call it and what to expect.

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 86%, so the schema carries most parameter documentation; baseline is 3. The description adds meaningful semantic context for query and id: query can be broad and is auto-ranked before x402, while id is for deterministic exact-product calls. This helps an agent choose the right calling mode beyond the raw schema.

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 names a specific verb and resource: identity-matched market intelligence for Japanese anime collectibles, returning low/median/high asking prices, offer count, freshness, and best matched listing. It also differentiates itself from generic marketplace search by emphasizing rejection of wrong editions and name collisions, so an agent can distinguish it from siblings like listing_match or price_history.

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 gives explicit when-to-use conditions ('when an agent needs current value, resale context or matched asking prices'), explicit not-to-use conditions ('Do not use for anime news, plot, streaming or character biography'), and names the preferred alternative when the signal is insufficient ('otherwise prefer Full Intelligence'). This is 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 / 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