Skip to main content
Glama

NovaPixel LexGrid

incoterms_cost_allocator

Deterministic allocation of transport, insurance, export/import clearance and risk transfer points across all 11 official ICC Incoterms 2020 rules.

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
incotermYes
namedPlaceYesNamed port or place of destination/delivery
goodsPriceEurYesBase goods price in EUR
cargoInsuranceEurNo
exportPackagingEurNo
finalInlandDeliveryEurNo
inlandFreightOriginEurNo
importDutiesAndTaxesEurNo
exportCustomsClearanceEurNo
internationalMainFreightEurNo
destinationTerminalHandlingEurNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Deterministic' hints that results are computed rather than fetched, but the description never states that the tool is side-effect-free, what happens when optional cost components are omitted, or what shape the allocation output takes despite there being no output schema.

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?

A single front-loaded sentence with no filler, and the key qualifier ('Deterministic') appears early. It is efficient but offers no structure beyond one clause for a tool with 11 inputs and no output schema.

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

Completeness2/5

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

Given 11 parameters at 18% schema coverage, no annotations, and no output schema, the description should explain required vs optional cost inputs, defaulting behavior, and the composition of the returned allocation. None of that is present, so the definition is incomplete for the tool's complexity.

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

Parameters2/5

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

Schema description coverage is only 18% and the description adds essentially nothing: it does not explain that incoterm drives which cost components apply, what namedPlace is used for, or how the eight optional EUR-denominated cost fields combine. Only the broad categories (transport, insurance, clearance) loosely echo parameter names, leaving most of the 11 parameters undocumented.

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 ('Deterministic allocation') and a specific resource ('transport, insurance, export/import clearance and risk transfer points across all 11 official ICC Incoterms 2020 rules'), which is enough for an agent to know this computes a cost/risk breakdown for a chosen Incoterm. It does not explicitly distinguish itself from the siblings, though those cover unrelated domains (emissions, export control, HS validation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no exclusions, no prerequisites, and no mention of alternatives. The agent must infer from the sentence alone that this is the tool for Incoterm cost allocation rather than, say, tariff validation.

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