Skip to main content
Glama

customswise

by io.github.giachi85it-ux

classify_product

Expert-verified EU/Italy customs classification support. Give a plain-language product description and get the likely HS/CN tariff heading orientation, the classification reasoning/notes, and any import-restriction flags — reviewed and signed by a licensed customs professional. Use it before shipping cross-border to avoid a wrong HS code, which causes fines, seized goods and back-duties. Guidance only, NOT a legally binding Tariff Information (BTI/ITV); genuinely ambiguous cases are flagged for expert escalation. Cost: $0.50 per call, paid automatically via x402 (USDC micropayment over HTTP 402).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoPlain-language description of the product to classify — include material, function and form for a better match, e.g. 'stainless steel vacuum flask with plastic lid' or 'men's cotton knitted t-shirt'.
langNoResponse language: 'en' (default) or 'it'.

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden. It discloses the expert-review process, non-binding nature, escalation of ambiguous cases, and the $0.50 x402/USDC micropayment over HTTP 402. This is unusually transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: purpose first, then usage context, then caveats, then cost. Each sentence adds necessary information and there is no filler or redundancy.

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?

Despite no output schema, the description enumerates the return contents: heading orientation, reasoning/notes, and restriction flags. It also covers cost, legal caveat, escalation behavior, and fully leverages the schema for parameters. Nothing critical is missing for an agent to invoke and interpret the result.

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?

The schema already covers both parameters fully, including the q description and lang default. The tool description restates the plain-language input concept but adds no parameter-specific meaning beyond the schema, so the baseline score of 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?

The description states a specific action and resource: it classifies a product into a likely HS/CN tariff heading and returns reasoning and import-restriction flags. It clearly distinguishes this tool from generic tariff lookup by emphasizing expert review, signature, and guidance-only status.

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?

It gives clear usage context: use before shipping cross-border to avoid wrong HS codes, and explicitly warns it is not a legally binding BTI/ITV. However, it does not name sibling tools such as get_tariff or ask_customs or explain when to prefer them.

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

All customswise toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Each tool targets a distinct customs sub-domain (classification, tariff, restrictions, origin, procedures), but ask_customs is a general-purpose fallback that intentionally overlaps with several specialized tools, and classify_product also surfaces restriction flags alongside check_restrictions. This creates minor boundary ambiguity, though the descriptions largely clarify which tool to choose.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: ask_customs, check_restrictions, classify_product, get_origin_rule, get_procedure, get_tariff, list_catalog. The naming is uniform and predictable with no mixed conventions or vague verbs.

Tool Count5/5

Seven tools is a well-scoped size for a customs advisory server. Each tool represents a meaningful category of customs knowledge, and none feel redundant or unnecessary. The free list_catalog tool also helps orient users without adding clutter.

Completeness4/5

The tool surface covers the major customs advisory areas: classification, duty/VAT, restrictions/sanctions, preferential origin, special procedures, and general Q&A. Minor gaps exist—such as dedicated customs valuation or post-clearance assistance—but ask_customs can serve as a catch-all for those edge cases, so the coverage is solid overall.

Resources