Skip to main content
Glama

incoterms_cost_allocator

Read-onlyIdempotent

[Deterministic international trade rules engine. Pure calculation, read-only, side-effect free]. Allocates transport costs, marine cargo insurance, export/import customs clearance fees, terminal handling charges, and exact legal transfer of risk points across all 11 official ICC Incoterms 2020 rules (EXW, FCA, CPT, CIP, DAP, DPU, DDP, FAS, FOB, CFR, CIF). Usage: Use this tool to compare seller vs buyer cost responsibilities and risk handoff milestones in international commercial contracts. Returns: JSON object with { incoterm: string, sellerCostEur: number, buyerCostEur: number, riskTransferPoint: string, mandatoryInsuranceRequired: boolean, costBreakdown: object }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "incoterm": "<incoterm>",
      "namedPlace": "<namedPlace>",
      "goodsPriceEur": "<goodsPriceEur>"
    },
    "name": "incoterms_cost_allocator"
  }
}

Input Schema

NameRequiredDescriptionDefault
incotermYesOfficial ICC Incoterms 2020 3-letter rule code
namedPlaceYesNamed port or place of destination/delivery (e.g. Port of Rotterdam, Milan Warehouse)
goodsPriceEurYesBase goods price in EUR
cargoInsuranceEurNoMarine/cargo transit insurance in EUR
exportPackagingEurNoExport packaging cost in EUR
finalInlandDeliveryEurNoFinal inland delivery transport to buyer premises in EUR
inlandFreightOriginEurNoInland transport to origin port/terminal in EUR
importDutiesAndTaxesEurNoDestination import customs duties and clearance fees in EUR
exportCustomsClearanceEurNoExport customs declarations and duties in EUR
internationalMainFreightEurNoInternational main carriage freight in EUR
destinationTerminalHandlingEurNoDestination port terminal handling charges (THC) in EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description largely restates that ('Pure calculation, read-only, side-effect free') while adding the useful determinism guarantee. It does not disclose how the eight optional cost inputs behave when omitted (assumed zero? error?), which is the key behavioral unknown for an 11-parameter calculator.

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 three-part structure (tag line, Usage, Returns) is front-loaded and easy to scan, and the explicit return shape is valuable given no output schema exists. The bracketed preamble partially duplicates annotation data, which is minor waste.

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 stateless calculator with no output schema, the description supplies the return object's fields and types, which is exactly what an agent needs to consume the result. The remaining gap is omission/default behavior for the eight optional cost parameters.

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 description coverage is 100%, so the schema already defines every parameter, including the incoterm enum and the namedPlace example. The description's category listing (transport, insurance, customs, THC) broadly maps to the inputs but adds no rules about defaults, currency assumptions, or which cost buckets are seller vs buyer supplied.

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?

The description uses a specific verb ('Allocates') plus an enumerated resource list (transport, marine insurance, customs clearance, THC, risk transfer points) scoped to all 11 ICC Incoterms 2020 rules, so the agent knows exactly what the tool computes. It never explicitly contrasts itself with the sibling tools (taric_hs_validator, cbam_embedded_emissions, dual_use_export_control), though the 'international trade rules engine' framing makes the domain distinct.

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?

'Use this tool to compare seller vs buyer cost responsibilities and risk handoff milestones in international commercial contracts' gives a clear context for invocation. There are no explicit exclusions or named alternatives, so the agent must infer that HS-code validation or emissions work belongs to siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources