Skip to main content
Glama

Import Landed Unit Cost

bpj_import_landed_unit_cost
Read-onlyIdempotent

Apply a supplied duty rate to merchandise plus freight and insurance, then spread handling and duty over purchased units.

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": {
      "invoice": "<invoice>",
      "carriage": "<carriage>",
      "duty": "<duty>",
      "handling": "<handling>",
      "actualQty": "<actualQty>"
    },
    "name": "bpj_import_landed_unit_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
dutyYes
invoiceYes
carriageYes
handlingYes
actualQtyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The read-only, idempotent, non-destructive, closed-world annotations already establish a safe local calculation, and the description usefully adds the duty base and allocation sequence. It does not disclose rounding, result representation, or behavior when actualQty is zero even though the schema permits zero.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is compact, front-loaded with the calculation, and contains no filler. Its two-step wording communicates substantial information efficiently, though the final allocation phrase is slightly compressed.

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

Completeness3/5

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

For a simple five-parameter calculator, the description supplies the main computational idea and the annotations cover its safety profile. However, with no output schema, the omission of an explicit full formula and result form matters, and zero-quantity and rounding behavior remain undocumented.

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

Parameters4/5

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

Despite 0% schema description coverage, the description connects all five inputs to the calculation and adds meaning beyond their titles by defining the dutiable base and purchased-unit denominator. It still leaves whether invoice and carriage must be shipment totals, currency consistency, and the valid practical quantity range unstated.

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 identifies a specific import-cost calculation: duty is applied to "merchandise plus freight and insurance," with handling and duty then allocated over purchased units. This distinguishes the landed-cost calculation from the other cost siblings, although it never explicitly states that the result is a full per-unit landed cost.

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

Usage Guidelines3/5

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

The required cost components and duty-rate scenario imply when the tool is useful, namely calculating an imported purchase's unit cost from supplied totals. There is no explicit when-to-use guidance, prerequisite such as consistent currency totals, or comparison with another costing tool.

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.