ANIME INTELLIGENCE

ANIME INTELLIGENCE - Landed Cost for Japan or International Buyer

landed_cost

Read-onlyIdempotent

Destination-aware purchase cost for Japanese anime collectibles. Supports Japan buyers explicitly and cross-border buyers conservatively, returning known item/shipping totals and refusing to invent unavailable duty, tax or brokerage amounts. WHEN TO USE: Use when an agent is ready to buy and must compare the actual payable route for a Japan-based buyer or a cross-border buyer. Japan is a first-class destination, not a fallback case. WHY PAY: Pay when the cheapest sticker price may not be the cheapest transaction after shipping or cross-border costs. The service identifies what is known and what remains unknown. BUYER OUTCOME: A destination-aware known total with uncertainty surfaced explicitly. Price: 0.02 USDC via x402. Selection triggers: landed cost, total cost, shipping to Japan, shipping to US, final price, all-in cost, import duty, tax included. Common agent queries: total cost for a buyer in Japan | landed cost of this anime figure to the US | what will I actually pay including known shipping | compare Japan domestic and overseas purchase cost. 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"
+]

AddedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond that: it states the tool 'refusing to invent unavailable duty, tax or brokerage amounts' and surfaces uncertainty explicitly. It also discloses the payment requirement (0.02 USDC via x402), which is a critical behavioral trait for an agent. No contradictions 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 long but well-structured with clear headers (WHEN TO USE, WHY PAY, BUYER OUTCOME, Price, Selection triggers, Common queries). It front-loads the core purpose and then provides practical trigger examples. Some sections like 'WHY PAY' could be trimmed, but overall it is organized and each part adds useful context for an agent. It earns a 4 rather than a 5 due to slight verbosity.

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 all necessary context: when to use it, what it returns (known totals with surfaced uncertainty), limitations (refuses to invent amounts), payment details, and examples. It explicitly contrasts with Full Intelligence and lists do-not-use cases. The output schema is present, so return format doesn't need to be in the description. Nothing essential is missing.

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 most parameters are already documented. The description adds meaningful context for key parameters: it explains that 'query' can be a broad multilingual description and is auto-ranked, and that 'buyer_country' drives country-aware routing and uncertainty. It also clarifies the 'id' parameter for deterministic calls. This goes beyond the schema and compensates for the few undocumented parameters, though not perfectly, hence a 4.

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 verb and resource: 'Destination-aware purchase cost for Japanese anime collectibles.' It clearly distinguishes itself from siblings by explicitly naming Full Intelligence as the alternative when a single signal doesn't fully answer the task, and it lists selection triggers that map to its purpose. This is far from a tautology and leaves no doubt about what the tool does.

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 a dedicated 'WHEN TO USE' section, states 'Use this specialist tool when this single signal fully answers the task; otherwise prefer Full Intelligence,' and lists 'Selection triggers' and 'Common agent queries.' It also explicitly says 'Do not use for anime news, plot, streaming or character biography questions,' giving clear exclusions. This is exemplary usage 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.