Skip to main content
Glama

customs_valuation

Compute the correct dutiable base under WTO Customs Valuation: adjust invoice price for incoterm, add statutory elements like assists and royalties, and apply CIF or FOB basis per country.

Instructions

Compute the correct DUTIABLE BASE on which the duty is charged — it is NOT just the invoice. Under the WTO Customs Valuation Agreement, give the destination country + invoice price + Incoterm and it builds the TRANSACTION VALUE: it normalises the price to an FOB-origin base (stripping freight/insurance/destination/duty a CIF or DDP price already carries), then ADDS the statutory additions importers forget — ASSISTS (free tooling/moulds/design — inflate the base), royalties, SELLING commission, packing — while EXCLUDING buying commission and post-import costs, and applies the COUNTRY BASIS: CIF (EU & most — international freight+insurance IN the base) vs FOB (US — excluded). It returns the line-by-line base, the duty on the correct base vs the naive invoice (the over/under-payment), and the DEDUCTIVE (resale-back-calc) and COMPUTED (cost build-up) methods when there is no transaction value. Honest (regla 7): INDICATIVE model of the method hierarchy & adjustments; related-party tests, first-sale and assist apportionment are case-specific — NOT a customs ruling or legal advice. PREMIUM: pay per call with x402 (USDC on Base) or a prepaid key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dest_countryYesDestination country ISO2 (US, DE, GB, …). REQUIRED — sets the CIF/FOB basis.
invoice_price_usdNoThe price actually paid/payable (total, or per-unit if per_unit=true). REQUIRED for transaction value.
quantity_unitsNoQuantity of units (for per-unit assists apportionment & per-unit output). Optional; default 1.
per_unitNoIs invoice_price_usd a PER-UNIT figure? Optional; default false (total).
incotermNoIncoterm of the price (EXW/FOB/CIF/DDP…). Optional; default FOB.
methodNo'transaction-value' (default), 'deductive' or 'computed'.
assists_usdNoAssists supplied free (tooling/moulds/materials/design), TOTAL USD — ADD to base. Optional.
royalties_usdNoRoyalties/licence fees that are a condition of sale, TOTAL USD. Optional.
selling_commission_usdNoSelling commission (to seller's agent), TOTAL USD — dutiable. Optional.
buying_commission_usdNoBuying commission (to buyer's own agent), TOTAL USD — NOT dutiable (shown excluded). Optional.
packing_usdNoPacking & containers cost, TOTAL USD. Optional.
international_freight_usdNoInternational freight to the import port, TOTAL USD (in base on CIF basis only). Optional.
insurance_usdNoInternational insurance, TOTAL USD (in base on CIF basis only). Optional.
post_import_transport_usdNoPost-import transport/destination charges baked into a DAP/DDP price, TOTAL USD — stripped out. Optional.
baked_import_duty_usdNoImport duty/tax baked into a DDP price, TOTAL USD — stripped out. Optional.
duty_rate_pctNoModeled duty rate (0.075 or 7.5) to value the over/under-payment vs the naive invoice. Optional.
resale_price_usdNoDeductive method: destination unit resale price (USD).
resale_margin_pctNoDeductive: resale gross margin to deduct (0.30). Optional; default 0.30.
deductible_inland_usdNoDeductive: per-unit post-import freight+duties to deduct (USD). Optional.
computed_unit_cost_usdNoComputed method: built-up unit cost (materials+fabrication+profit+expenses), USD.
Behavior5/5

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

No annotations, so description fully covers behavior: normalizes to FOB base, adds assists, excludes buying commission, applies country basis. Discloses it's an indicative model, not legal advice.

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?

Long but information-dense. Front-loaded with purpose. Every sentence adds value given complexity. Slightly verbose but acceptable.

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?

Describes return values (line-by-line base, duty comparison, deductive/computed methods). With 20 parameters and no output schema, description adequately covers what the tool does and outputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% but description adds context beyond, e.g., which parameters required for each method, how they affect calculation. Provides practical usage guidance.

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?

Clearly states the tool computes the dutiable base for customs valuation, not just invoice price, using WTO methods. Distinguishes from siblings like customs_optimization by focusing on valuation.

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?

Describes when to use: provide destination country, invoice price, and Incoterm. Hints at alternatives (deductive, computed) and notes limitations (not legal advice). Lacks explicit when-not-to-use but informative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Baneado98/freight-pulse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server