Skip to main content
Glama

Triplicate – export documents

Create export documents

create_trade_documents
Read-only

Use when a user has order data (seller, buyer and items; prices, cartons and weights if known) and wants a proforma invoice, commercial invoice, packing list or shipping instruction; open_document also opens a purchase order, sales contract or certificate of origin, and open_form one of the extra forms. Create a matching proforma invoice, commercial invoice, packing list and shipping instruction from one set of order data. Returns a link to Triplicate's free generator with everything filled in (the user reviews it and saves the PDF), plus totals (amount, cartons, net/gross weight, CBM) and checks (missing fields, HS code format, Incoterms freight/insurance consistency). Nothing is stored.

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": {
      "seller": "<seller>",
      "buyer": "<buyer>",
      "items": "<items>"
    },
    "name": "create_trade_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNo
buyerYesBuyer / consignee / importer
itemsYes
termsNo
notifyNoNotify party, if different from the buyer
sellerYesSeller / shipper / exporter
signerNo
chargesNo
remarksNoOptional remarks printed on the documents, e.g. 'SAMPLES OF NO COMMERCIAL VALUE, NOT FOR RESALE. VALUE FOR CUSTOMS PURPOSES ONLY.'
sold_toNoOnly if the buyer (sold to) is a different company from the consignee in 'buyer', e.g. a trading company buying for a factory: printed as BUYER (SOLD TO) on the invoice, the buyer on the proforma and sales contract
documentNo
languageNoLanguage of the generator page the link opens (documents are in English)en
shipmentNo
hs_totalsNoAlso print totals by HS code (quantity, value, cartons, weights) on the invoice and packing list, for the customs broker's entry lines
open_formNoAlso open one of the generator's extra forms with this data: VGM declaration (SOLAS, needs shipment.containers), ISF (10+2) data for a US buyer, USMCA/CUSMA certification of origin, packing declaration for sea containers to Australia, draft (bill of exchange), beneficiary's certificate, credit/debit note, shipping advice e-mail, or a return/repair invoice made from this invoice (the original invoice number, date and waybill as reference; the buyer as shipper when goods come back). Each has 3 free uses (the shipping advice has no limit).
manufacturerNoWho made the goods, printed on the commercial invoice with its MID code (US shipments: carriers and CBP ask for it; textile and apparel entries must show it). The generator suggests the MID from 19 CFR Part 102 if mid is empty
open_documentNopi proforma invoice, ci commercial invoice, pl packing list, si shipping instruction, sc sales contract (seller and buyer sign; the remarks become its other terms), co certificate of origin (non-preferential: the exporter's declaration, with space for a chamber of commerce to certify it), po purchase order (the buyer's order to the supplier: buyer = issuer, seller = supplier)ci
imperial_unitsNoAlso show weights in pounds and volume in cubic feet on the packing list and shipping instruction (for US buyers)
shipping_marksNoOptional; generated from buyer, destination and carton count if empty
letter_of_creditNoTerms of the letter of credit (from MT700: 20, 31C, 32B, 39A, 44C, 31D, 48, 43P, 45A); the generator checks the documents against them (not among the free features)
origin_statementNoPreferential origin statement printed on the commercial invoice in the agreement's exact wording (3 free uses). Only for goods that meet the agreement's rules of origin.
destination_countryNoISO 3166-1 alpha-2 code of the importing country (optional; otherwise taken from the port of discharge): adds that country's invoice rules to the checks

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / items / items / properties / unit / enum
      Previous value: -[
      -  "PCS",
      -  "SETS",
      -  "BOXES",
      -  "PAIRS",
      -  "KG",
      -  "M"
      -]New value: +[
      +  "PCS",
      +  "SETS",
      +  "BOXES",
      +  "PAIRS",
      +  "DOZ",
      +  "KG",
      +  "MT",
      +  "M",
      +  "SQM",
      +  "CBM",
      +  "L",
      +  "ROLLS",
      +  "BAGS"
      +]
  2. Changed23 schema fields changed
    • addedInput schema / properties / destination_country
      Added value: +{
      +  "description": "ISO 3166-1 alpha-2 code of the importing country (optional; otherwise taken from the port of discharge): adds that country's invoice rules to the checks",
      +  "type": "string"
      +}
    • addedInput schema / properties / hs_totals
      Added value: +{
      +  "default": false,
      +  "description": "Also print totals by HS code (quantity, value, cartons, weights) on the invoice and packing list, for the customs broker's entry lines",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / items / items / properties / free_of_charge
      Added value: +{
      +  "description": "Sent free (samples, gifts): the value stays on the documents for customs and is taken off the amount payable",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / items / items / properties / gtin
      Added value: +{
      +  "description": "GTIN / EAN / UPC barcode number, if the product has one",
      +  "type": "string"
      +}
    • addedInput schema / properties / items / items / properties / manufacturer_product_code
      Added value: +{
      +  "description": "Manufacturer's own product code (part number)",
      +  "type": "string"
      +}
    • addedInput schema / properties / items / items / properties / not_originating
      Added value: +{
      +  "description": "With origin_statement: this item does not qualify and is marked as not covered by the statement",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / items / items / properties / packed_with_previous
      Added value: +{
      +  "description": "Assorted cartons: packed in the same cartons as the item before it, whose carton weights include this item; leave its carton fields empty",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / items / items / properties / section_232_metal_origin
      Added value: +{
      +  "description": "US shipments of steel or aluminium articles: the countries where the steel was melted and poured or the aluminium smelted and cast, e.g. 'STEEL MELT AND POUR: KR'; printed under the description",
      +  "type": "string"
      +}
    • addedInput schema / properties / items / items / properties / sku
      Added value: +{
      +  "description": "Seller's product code, printed under the description (EU import declarations for distance sales need it from 1 November 2026)",
      +  "type": "string"
      +}
    • addedInput schema / properties / letter_of_credit
      Added value: +{
      +  "description": "Terms of the letter of credit (from MT700: 20, 31C, 32B, 39A, 44C, 31D, 48, 43P, 45A); the generator checks the documents against them (not among the free features)",
      +  "properties": {
      +    "amount": {
      +      "type": "number"
      +    },
      +    "expiry_date": {
      +      "description": "YYYY-MM-DD",
      +      "type": "string"
      +    },
      +    "goods_description": {
      +      "type": "string"
      +    },
      +    "issue_date": {
      +      "description": "YYYY-MM-DD",
      +      "type": "string"
      +    },
      +    "latest_shipment_date": {
      +      "description": "YYYY-MM-DD",
      +      "type": "string"
      +    },
      +    "number": {
      +      "type": "string"
      +    },
      +    "partial_shipments": {
      +      "enum": [
      +        "allowed",
      +        "not_allowed"
      +      ],
      +      "type": "string"
      +    },
      +    "presentation_days": {
      +      "type": "number"
      +    },
      +    "show_on_documents": {
      +      "description": "Print the L/C number and date on the documents",
      +      "type": "boolean"
      +    },
      +    "tolerance_percent": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "number"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / manufacturer
      Added value: +{
      +  "description": "Who made the goods, printed on the commercial invoice with its MID code (US shipments: carriers and CBP ask for it; textile and apparel entries must show it). The generator suggests the MID from 19 CFR Part 102 if mid is empty",
      +  "properties": {
      +    "city": {
      +      "type": "string"
      +    },
      +    "country_code": {
      +      "description": "ISO 3166-1 alpha-2",
      +      "type": "string"
      +    },
      +    "mid": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "province": {
      +      "description": "Canada only, e.g. ON",
      +      "type": "string"
      +    },
      +    "same_as_seller": {
      +      "type": "boolean"
      +    },
      +    "street": {
      +      "description": "Street address line with the building number",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / open_form
      Added value: +{
      +  "description": "Also open one of the generator's extra forms with this data: VGM declaration (SOLAS, needs shipment.containers), ISF (10+2) data for a US buyer, USMCA/CUSMA certification of origin, packing declaration for sea containers to Australia, draft (bill of exchange), beneficiary's certificate, credit/debit note, shipping advice e-mail, or a return/repair invoice made from this invoice (the original invoice number, date and waybill as reference; the buyer as shipper when goods come back). Each has 3 free uses (the shipping advice has no limit).",
      +  "enum": [
      +    "vgm_declaration",
      +    "isf_data",
      +    "usmca_certification",
      +    "packing_declaration_australia",
      +    "bill_of_exchange",
      +    "beneficiary_certificate",
      +    "credit_note",
      +    "shipping_advice",
      +    "return_invoice"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / origin_statement
      Added value: +{
      +  "description": "Preferential origin statement printed on the commercial invoice in the agreement's exact wording (3 free uses). Only for goods that meet the agreement's rules of origin.",
      +  "properties": {
      +    "agreement": {
      +      "enum": [
      +        "eu_korea",
      +        "uk_korea",
      +        "eu_vietnam",
      +        "eu_singapore",
      +        "eu_japan",
      +        "uk_japan",
      +        "eu_uk",
      +        "eu_canada",
      +        "korea_efta",
      +        "eu_gsp",
      +        "uk_dcts"
      +      ],
      +      "type": "string"
      +    },
      +    "number": {
      +      "description": "Approved exporter's authorisation number (EU-Korea, UK-Korea, EU-Vietnam; may be empty up to EUR 6,000 per consignment), REX number (EU GSP, EU-Canada, EU-Singapore; EU exporters), UEN (Singapore exporters, EU-Singapore), Exporter Reference No. (EU-Japan, UK-Japan, EU-UK: REX or GB EORI), Business Number (Canadian exporters) or customs identification number (UK DCTS)",
      +      "type": "string"
      +    },
      +    "origin": {
      +      "description": "Origin as written in the statement, e.g. Korea, EU, Japan, European Union",
      +      "type": "string"
      +    },
      +    "origin_criterion": {
      +      "description": "EU-Japan and UK-Japan: A, B, C1-C4, D or E. EU GSP and UK DCTS: P, or W followed by the HS heading (e.g. W 9618). Not used by the other agreements",
      +      "type": "string"
      +    },
      +    "period_from": {
      +      "description": "YYYY-MM-DD; EU-Japan, UK-Japan, EU-UK, CETA: one statement for several shipments of identical products (12 months at most)",
      +      "type": "string"
      +    },
      +    "period_to": {
      +      "description": "YYYY-MM-DD",
      +      "type": "string"
      +    },
      +    "place": {
      +      "description": "Place printed with the date, e.g. Seoul (default: the port of loading's city)",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "agreement"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / shipment / properties / containers
      Added value: +{
      +  "description": "Sea containers (FCL): printed as CONTAINER / SEAL NO. on the invoice, packing list and shipping instruction; the numbers are checked against their ISO 6346 check digit. In the generator, More > VGM declaration (3 free uses) makes the SOLAS VGM form from them",
      +  "items": {
      +    "properties": {
      +      "carton_numbers": {
      +        "description": "Cartons in this container, e.g. '1-500': the packing list then shows each container's cartons, weights and CBM",
      +        "type": "string"
      +      },
      +      "number": {
      +        "description": "e.g. MSKU1234565",
      +        "type": "string"
      +      },
      +      "seal": {
      +        "type": "string"
      +      },
      +      "size_type": {
      +        "description": "e.g. 20GP, 40HC, 45G1",
      +        "type": "string"
      +      },
      +      "tare_kg": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "maxItems": 40,
      +  "type": "array"
      +}
    • addedInput schema / properties / shipment / properties / duties_paid_by
      Added value: +{
      +  "description": "Courier invoices: who pays the import duties and taxes (DDP: sender)",
      +  "enum": [
      +    "receiver",
      +    "sender",
      +    "third_party"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / shipment / properties / export_declaration_number
      Added value: +{
      +  "description": "Export declaration, shipping bill or AES ITN number, printed in the remarks box",
      +  "type": "string"
      +}
    • addedInput schema / properties / shipment / properties / original_invoice_date
      Added value: +{
      +  "description": "YYYY-MM-DD",
      +  "type": "string"
      +}
    • addedInput schema / properties / shipment / properties / original_invoice_number
      Added value: +{
      +  "description": "Goods going back (reason_for_export repair_and_return, returned_goods or temporary_export): the original shipment's invoice number, printed as ORIGINAL SHIPMENT",
      +  "type": "string"
      +}
    • addedInput schema / properties / shipment / properties / original_waybill_number
      Added value: +{
      +  "description": "The original shipment's AWB or B/L number",
      +  "type": "string"
      +}
    • addedInput schema / properties / shipment / properties / pallets
      Added value: +{
      +  "description": "If the cartons are palletized: the documents then show e.g. 4 PLTS (101 CTNS), gross weight with the empty pallets and the loaded pallets' volume",
      +  "properties": {
      +    "count": {
      +      "type": "number"
      +    },
      +    "empty_pallet_weight_kg": {
      +      "type": "number"
      +    },
      +    "height_cm": {
      +      "description": "Loaded height",
      +      "type": "number"
      +    },
      +    "length_cm": {
      +      "type": "number"
      +    },
      +    "width_cm": {
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / shipment / properties / reason_for_export
      Added value: +{
      +  "description": "Printed on courier invoices (box 10)",
      +  "enum": [
      +    "sale",
      +    "sample",
      +    "gift",
      +    "repair_and_return",
      +    "returned_goods",
      +    "temporary_export"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / shipment / properties / waybill_number
      Added value: +{
      +  "description": "Air waybill or courier tracking number, printed in box 6",
      +  "type": "string"
      +}
    • addedInput schema / properties / sold_to
      Added value: +{
      +  "description": "Only if the buyer (sold to) is a different company from the consignee in 'buyer', e.g. a trading company buying for a factory: printed as BUYER (SOLD TO) on the invoice, the buyer on the proforma and sales contract",
      +  "properties": {
      +    "address": {
      +      "description": "Full address, lines separated by \\n",
      +      "type": "string"
      +    },
      +    "email": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "tax_id": {
      +      "description": "Tax / VAT / business registration number",
      +      "type": "string"
      +    },
      +    "tel": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name"
      +  ],
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / open_document / description
      Previous value: -"pi proforma invoice, ci commercial invoice, pl packing list, si shipping instruction, sc sales contract (seller and buyer sign; the remarks become its other terms), po purchase order (the buyer's order to the supplier: buyer = issuer, seller = supplier)"New value: +"pi proforma invoice, ci commercial invoice, pl packing list, si shipping instruction, sc sales contract (seller and buyer sign; the remarks become its other terms), co certificate of origin (non-preferential: the exporter's declaration, with space for a chamber of commerce to certify it), po purchase order (the buyer's order to the supplier: buyer = issuer, seller = supplier)"
    • changedInput schema / properties / open_document / enum
      Previous value: -[
      -  "pi",
      -  "ci",
      -  "pl",
      -  "si",
      -  "po",
      -  "sc"
      -]New value: +[
      +  "pi",
      +  "ci",
      +  "pl",
      +  "si",
      +  "po",
      +  "sc",
      +  "co"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / open_document / description
      Previous value: -"pi proforma invoice, ci commercial invoice, pl packing list, si shipping instruction, po purchase order (the buyer's order to the supplier: buyer = issuer, seller = supplier)"New value: +"pi proforma invoice, ci commercial invoice, pl packing list, si shipping instruction, sc sales contract (seller and buyer sign; the remarks become its other terms), po purchase order (the buyer's order to the supplier: buyer = issuer, seller = supplier)"
    • changedInput schema / properties / open_document / enum
      Previous value: -[
      -  "pi",
      -  "ci",
      -  "pl",
      -  "si",
      -  "po"
      -]New value: +[
      +  "pi",
      +  "ci",
      +  "pl",
      +  "si",
      +  "po",
      +  "sc"
      +]
  5. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / country_of_origin
      Added value: +{
      +  "description": "Only if this item's origin differs from shipment.country_of_origin; the documents then show the origin per item",
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / imperial_units
      Added value: +{
      +  "default": false,
      +  "description": "Also show weights in pounds and volume in cubic feet on the packing list and shipping instruction (for US buyers)",
      +  "type": "boolean"
      +}
  7. Changed2 schema fields changed
    • changedInput schema / properties / open_document / description
      Previous value: -"pi proforma invoice, ci commercial invoice, pl packing list, si shipping instruction"New value: +"pi proforma invoice, ci commercial invoice, pl packing list, si shipping instruction, po purchase order (the buyer's order to the supplier: buyer = issuer, seller = supplier)"
    • changedInput schema / properties / open_document / enum
      Previous value: -[
      -  "pi",
      -  "ci",
      -  "pl",
      -  "si"
      -]New value: +[
      +  "pi",
      +  "ci",
      +  "pl",
      +  "si",
      +  "po"
      +]
  8. Changed2 schema fields changed
    • addedInput schema / properties / remarks
      Added value: +{
      +  "description": "Optional remarks printed on the documents, e.g. 'SAMPLES OF NO COMMERCIAL VALUE, NOT FOR RESALE. VALUE FOR CUSTOMS PURPOSES ONLY.'",
      +  "type": "string"
      +}
    • changedInput schema / properties / terms / 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"
      +]
  9. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Nothing is stored.' It adds real value by disclosing the return shape (a generator link the user reviews and saves, plus totals and checks) and free-use limits on extras, though it could say more about failure modes or what the checks block.

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?

Front-loads the trigger condition and the core action, then packs return behavior into a second dense sentence. Semicolon-heavy but every clause (totals, checks, no storage) contributes information; slightly heavy but not padded.

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 22-parameter, heavily nested tool with no output schema, the description explains the deliverable (link, totals, checks) and confirms nothing is persisted. The remaining burden is carried by the detailed schema; an agent has enough to call it correctly, though edge-case behavior on failed checks is unspecified.

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 68%, so the schema carries most parameter meaning; the description only summarizes the order-data inputs (prices, cartons, weights 'if known'). It does not add per-parameter semantics beyond what the property descriptions already provide, so baseline 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?

States a specific verb (create) and resource (proforma/commercial invoice, packing list, shipping instruction) and explicitly scopes what data is required (seller, buyer, items). It also names the sibling-adjacent options (open_document, open_form) so an agent can place it among related capabilities.

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

Usage Guidelines5/5

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

Opens with an explicit trigger: 'Use when a user has order data ... and wants a proforma invoice, commercial invoice, packing list or shipping instruction,' then distinguishes the alternate document paths via open_document and open_form. Clear when-to-use plus routing to alternatives.

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