Skip to main content
Glama

Triplicate – export documents

Export price under each Incoterms rule

calculate_export_price
Read-only

Use when a user has a unit cost and wants the price to quote under EXW, FCA, FOB, CFR, CIF, DAP, DPU or DDP. Build an export quotation price from unit cost, markup and shipment costs: totals and per-unit prices under EXW, FCA, FOB/FCA terminal, CFR/CPT, CIF/CIP, DAP, DPU and DDP, with the insurance premium (110% basis), import duty and VAT, and for each rule a link that opens Triplicate's generator with a proforma invoice at that price.

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": {
      "quantity": "<quantity>",
      "unit_cost": "<unit_cost>"
    },
    "name": "calculate_export_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNosea: FOB/CFR/CIF (loaded on board at a port); any: containers handed over at a terminal, air or road: FCA/CPT/CIPsea
costsNoShipment totals in the same currency (omit what does not apply)
currencyNoUSD
languageNoLanguage of the generator page the proforma links openen
quantityYesUnits in the shipment
unit_costYesSeller's cost per unit (product cost)
duty_basisNoCustoms value basis: cif (EU, UK, most countries) or fob (US, Canada, Australia)cif
markup_percentNoMarkup on cost, e.g. 25 for +25%
include_vat_in_ddpNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / currency / enum
      Previous value: -[
      -  "USD",
      -  "EUR",
      -  "GBP",
      -  "JPY",
      -  "CNY",
      -  "KRW",
      -  "VND"
      -]New value: +[
      +  "USD",
      +  "EUR",
      +  "GBP",
      +  "JPY",
      +  "CNY",
      +  "KRW",
      +  "VND",
      +  "AUD",
      +  "CAD",
      +  "CHF",
      +  "HKD",
      +  "SGD",
      +  "INR",
      +  "PKR",
      +  "BDT",
      +  "IDR",
      +  "THB",
      +  "MYR",
      +  "PHP",
      +  "AED",
      +  "SAR",
      +  "TRY",
      +  "BRL",
      +  "MXN",
      +  "ZAR",
      +  "NGN",
      +  "KES",
      +  "EGP"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds computation semantics the annotations cannot convey: insurance premium computed on a 110% basis, import duty and VAT handling, and that each rule yields a link opening the generator with a proforma invoice. That last point is valuable output behavior given there is no output schema, though the response format overall is only loosely characterized.

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 usage trigger is front-loaded in the first sentence, but the second sentence is a dense run-on that repeats the Incoterms list already named at the start, costing some efficiency without adding 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 9-parameter tool with nested cost objects, 78% schema coverage and no output schema, the description covers the main computation inputs and the shape of the result (per-rule totals, insurance, duty, VAT, generator links). Minor gaps remain around currency handling and how partial cost data affects results.

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 78%, so the schema already carries most parameter meaning. The description confirms key inputs (unit cost, markup, shipment costs) and the 110% insurance basis, but adds little for undocumented parameters such as import_duty_percent, include_vat_in_ddp and currency. Baseline 3 is appropriate.

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+resource ('Build an export quotation price') and enumerates exactly what is produced (totals and per-unit prices under each Incoterms rule). An agent can distinguish it from sibling tools like calculate_shipment or create_trade_documents without opening the schema.

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 when a user has a unit cost and wants the price to quote under EXW, FCA, FOB...' gives a clear triggering condition. It does not name an alternative tool or state when not to use it, so it falls short of the 5 bar.

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