ANIME INTELLIGENCE / AI PURCHASE INTELLIGENCE

PARTS INTELLIGENCE - Exact Part Lifecycle Compatibility and Sourcing

parts_intelligence

Read-onlyIdempotent

Paid exact-part intelligence for industrial and service parts. Resolves the canonical manufacturer part number before payment, then returns lifecycle, verified successor/substitute relationships, official evidence, sourcing observations and agent-ready merchant offers. Compatibility is never inferred from title similarity alone. WHEN TO USE: Use for industrial, MRO, service, appliance, camera, audio, tool, IT and other exact model-number parts when lifecycle, replacement, compatibility or sourcing evidence matters. WHY PAY: Pay for exact-part resolution plus evidence-gated lifecycle, replacement and sourcing intelligence. The service does not infer compatibility from similar names or dimensions. BUYER OUTCOME: An evidence-gated exact-part decision with verified lifecycle/replacement context and ranked merchant sourcing options. Price: 0.05 USDC via x402. Selection triggers: part number, MPN, discontinued part, successor, replacement, substitute, compatible, MRO, industrial part, source this part. Common agent queries: . 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

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

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.

Changed13 schema fields changedOct 24, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "query"
-    ]
-  },
-  {
-    "required": [
-      "part_number"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "query"
+    ]
+  },
+  {
+    "required": [
+      "id"
+    ]
+  }
+]

addedInput schema / properties / buyer_country

Added value: +{
+  "default": "JP",
+  "description": "ISO 3166-1 alpha-2 buyer destination. Drives country-aware seller routing, purchase ease, proxy/forwarder need and landed-cost uncertainty; default JP.",
+  "type": "string"
+}

addedInput schema / properties / id

Added value: +{
+  "description": "ANIME INTELLIGENCE canonical product UUID. Use for deterministic exact-product calls when already known.",
+  "type": "string"
+}

addedInput schema / properties / lang

Added value: +{
+  "default": "en",
+  "enum": [
+    "ja",
+    "en",
+    "zh",
+    "ko",
+    "es",
+    "fr",
+    "de"
+  ],
+  "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"
+}

removedInput schema / properties / manufacturer
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / part_number
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / postal_code

Added value: +{
+  "description": "Optional destination postal code for landed-cost context.",
+  "type": "string"
+}

addedInput schema / properties / query / description

Added 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."

addedInput schema / properties / query / examples

Added value: +[
+  "OMRON E2E-X5ME1",
+  "Mitsubishi Electric exact replacement part",
+  "Find verified successor and suppliers for this discontinued part"
+]

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "buyer_outcome": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "expected_output": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "intent": {
+    "type": "string"
+  },
+  "paid_x402_url": {
+    "type": "string"
+  },
+  "payment": {
+    "type": "string"
+  },
+  "price_usdc": {
+    "type": "number"
+  },
+  "why_pay": {
+    "type": "string"
+  }
+}

AddedOct 6, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Goes beyond the read-only/idempotent annotations by disclosing payment mechanics (0.05 USDC via x402, with canonical resolution and ranking occurring before payment) and the key constraint that compatibility is never inferred from title similarity alone. That is genuine behavioral context an agent could not get from annotations. It doesn't cover latency, failure modes, or rate limits.

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?

Runs long with redundant WHY PAY and BUYER OUTCOME sections restating the same value proposition. Worse, it includes an empty 'Common agent queries: .' fragment and off-topic anime exclusions, both of which waste the reader's attention in the most prominent position.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, and the description covers pricing, triggers and exclusions adequately. But the leftover anime boilerplate and the empty queries section leave the agent unsure whether this tool has any anime scope, which is a real completeness defect for a paid tool.

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 query, id, lang, listing_url, listing_title and buyer_country. The description adds only the broad-query auto-ranking behavior and the pre-payment resolution step, without clarifying the query-vs-id choice or landed-cost inputs. Baseline 3 is appropriate.

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?

States a specific verb+resource: resolves the canonical manufacturer part number and returns lifecycle, successor/substitute relationships, evidence, sourcing observations and merchant offers. That clearly distinguishes it from parts_search and parts_status. It loses a point because anime-related boilerplate ('Do not use for anime news, plot, streaming') muddies the scope of an industrial-parts tool.

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?

Provides an explicit WHEN TO USE block with concrete domains and selection triggers (MPN, discontinued part, successor, substitute, MRO), plus a routing rule to prefer Full Intelligence when the single signal doesn't fully answer the task. It stops short of 5 because the 'Common agent queries:' line is empty and the 'single signal fully answers the task' condition is vague.

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