ANIME INTELLIGENCE

ANIME INTELLIGENCE - Anime Figure Authenticity & Bootleg Risk

anime_authenticity

Read-onlyIdempotent

Pre-purchase counterfeit and listing-risk screening for Japanese anime collectibles. Cross-checks canonical identity, official references, price relationships and matched listing signals to flag bootleg risk, suspiciously cheap offers and identity mismatches. WHEN TO USE: Use when an offer is unusually cheap, the seller title is vague, official references are missing or Japanese and overseas listings disagree on identity. WHY PAY: Pay before recommending a suspicious offer when counterfeit, bootleg or wrong-edition risk could cause a bad purchase. BUYER OUTCOME: A pre-purchase risk screen tied to the exact collectible and listing context. Price: 0.02 USDC via x402. Selection triggers: fake, bootleg, counterfeit, authentic, genuine, suspicious, too cheap, wrong version, listing mismatch. Common agent queries: is this anime figure fake | is this Nendoroid a bootleg | check counterfeit risk before buying | does this listing match the official Japanese product | is this cheap anime figure listing suspicious. 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: -[
-  "Is this Nendoroid likely authentic?",
-  "Is this cheap anime collectible listing suspicious?"
-]New value: +[
+  "Is this cheap Nendoroid listing suspicious?",
+  "Bootleg risk for this ONE PIECE figure",
+  "Does this listing match the official Japanese product?"
+]

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: -[
-  "Is this figure likely authentic?",
-  "cheap Nendoroid listing"
-]New value: +[
+  "Is this Nendoroid likely authentic?",
+  "Is this cheap anime collectible listing suspicious?"
+]

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

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds meaningful context: it is a paid pre-purchase screen ('Price: 0.02 USDC via x402'), payment happens only after the service resolves and ranks the product, and it flags bootleg risk/identity mismatches. No contradiction with the non-destructive readOnlyHint.

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 verbose but well-structured with labeled sections (WHEN TO USE, WHY PAY, BUYER OUTCOME) and the core purpose is front-loaded. Some redundancy exists—common agent queries overlap with schema examples—but the organization makes the length navigable and useful.

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 paid specialist tool with 7 parameters and an output schema, the description covers invocation triggers, pricing, exclusions, and sibling routing. The presence of an output schema means return values do not need to be spelled out, and nothing needed to select or call this tool correctly 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 high (86%), and parameter-level descriptions in the schema already explain query types, listing_url, listing_title, and buyer_country. The prose description adds little beyond re-stating that broad multilingual queries are auto-ranked before payment, which is already in the query schema, so a baseline 3 is appropriate.

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 line states a specific function—'Pre-purchase counterfeit and listing-risk screening for Japanese anime collectibles'—with clear scope and outcome. It is further differentiated from siblings by naming Full Intelligence as the fallback for broader tasks and by listing bootleg/counterfeit triggers, so an agent can identify when this specialist tool applies.

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?

Explicit WHEN TO USE conditions are given ('unusually cheap, seller title vague, official references missing...') and a clear exclusion set ('Do not use for anime news, plot, streaming or character biography'). It also tells the agent to prefer Full Intelligence when the single signal does not fully answer the task, making routing unambiguous.

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.