Skip to main content
Glama
Sign In

mcp-server

by com.interzoid
OverviewDiscussionsAdmin

interzoid_customs_duty_rates

Read-onlyIdempotent

Import customs duty and tax rates for an HS code on a trade route (origin to destination country): MFN duty, preferential FTA rate, trade-remedy duties (anti-dumping, countervailing, Section 301), safeguard measures, import VAT or GST, special taxes, de minimis thresholds, and restrictions. For landed cost calculation, cross-border e-commerce, sourcing, and trade compliance. Cost: $0.35 USDC via x402.

Input Schema

NameRequiredDescriptionDefault
hscodeYesHarmonized System (HS) code, 6-digit minimum (up to 10-digit national extensions)
lookupYesDestination (import) country name or ISO code
originNoOrigin (export) country name or ISO code, for preferential FTA and trade-remedy rates. Optional but recommended.
languageNoOptional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Optional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.",
+  "enum": [
+    "fr",
+    "de",
+    "it",
+    "es",
+    "ja",
+    "pt",
+    "zh",
+    "ar",
+    "nl",
+    "el",
+    "tr",
+    "ko",
+    "sv",
+    "vi",
+    "th",
+    "id"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / lookup / description
      Previous value: -"Destination country name or ISO code"New value: +"Destination (import) country name or ISO code"
    • addedInput schema / properties / origin
      Added value: +{
+  "description": "Origin (export) country name or ISO code, for preferential FTA and trade-remedy rates. Optional but recommended.",
+  "examples": [
+    "China"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / hscode / examples
      Added value: +[
+  "8471.30"
+]
    • addedInput schema / properties / lookup / examples
      Added value: +[
+  "Germany"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new operational context: a $0.35 USDC x402 payment requirement, which an agent must know before invoking. It does not mention data freshness, rate limits, or what happens if the HS code or route is unknown.

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?

Two dense sentences, front-loaded with the resource and scope, followed by use cases and pricing. The long enumeration of duty types is justified because there is no output schema, though it reads as a comma-list rather than structured information.

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?

For a read-only lookup with no output schema, the description usefully enumerates the categories of data returned (MFN, FTA, anti-dumping/countervailing/Section 301, VAT/GST, de minimis, restrictions) and discloses the payment mechanism. Only the response shape and error/coverage behavior remain unspecified, which is a minor gap.

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 100%, with all four parameters — including the origin parameter's purpose for preferential FTA and trade-remedy rates and the language enum — documented in the schema itself. The description merely restates the field list already implied by the schema, adding no syntax or format detail, so baseline 3 applies.

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?

States a specific verb and resource ('Import customs duty and tax rates for an HS code on a trade route') and enumerates the exact duty/tax components returned. It is clearly distinguishable from sibling rate tools like interzoid_eu_vat_rates or interzoid_sales_use_tax_rates by the HS-code-plus-trade-route scope.

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?

Gives concrete use contexts (landed cost calculation, cross-border e-commerce, sourcing, trade compliance) so an agent knows when this is the right tool. However, it never names alternatives or exclusions — e.g., when to prefer interzoid_eu_vat_rates for plain VAT lookups — so it stops short of explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server 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