Moltline Shipping Maths

Landed Cost

landed_cost

Read-onlyIdempotent

Total what a unit really costs once freight, duty and fees are in. FREE.

Duty is applied to goods value, tax to goods plus duty plus freight (the common import treatment), and the order is spelled out in the response so you can check it against your own broker's method. Typical input {"unit_cost": 8.5, "quantity": 200, "freight_total": 640, "duty_pct": 6.5, "tax_pct": 0} returns {"goods": 1700.0, "duty": 110.5, "freight": 640.0, "tax": 0.0, "total_landed": 2450.5, "landed_unit_cost": 12.25, ...}.

Use before setting a price on imported stock. Not for the margin that price leaves you: that is the dropship server's margin_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": ""}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

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

Input Schema

Name	Required	Description
`tax_pct`	No	Import VAT or GST as a percentage of goods plus duty plus freight, e.g. 20. Default 0.
`duty_pct`	No	Import duty as a percentage of goods value, e.g. 6.5. Default 0.
`quantity`	No	Units in the shipment. Must be at least 1. Default 1.
`unit_cost`	Yes	Ex-works cost of one unit in your currency. Must be greater than 0.
`other_fees`	No	Brokerage, port and handling charges for the shipment. Default 0.
`freight_total`	No	Total freight and insurance for the whole shipment, not per unit. Default 0.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the safety profile is known. The description adds materially beyond that: it calls out that no protocol error is ever raised, describes the error-return shape and how to fix it, confirms retry safety after correction, and states that the calculation order appears in the response for verification.

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?

Purpose and usage context are front-loaded, and the example is compact and informative. A few phrases ("FREE.", the multi-line formatting) add mild noise, but overall it is dense with useful content rather than padded.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and the description correctly focuses on computation semantics, error behavior and retry safety. For a six-parameter, fully documented calculation tool, nothing an agent needs in order to invoke it correctly is missing.

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?

Schema coverage is 100%, so baseline is 3. The description earns above baseline by giving a worked input/output example and explaining the duty and tax bases (duty on goods value; tax on goods plus duty plus freight) in a form that is directly checkable, though the schema already documents those percentage bases.

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 opening sentence states a specific computation (total unit cost including freight, duty and fees), which is clear and actionable. It distinguishes itself from margin_check on the dropship server, but it does not differentiate itself from the shipping-focused sibling tools (rate_card, freight_class, dim_weight, etc.), so it falls short of the sibling-aware 5.

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?

It gives an explicit when-to-use ("Use before setting a price on imported stock") and an explicit when-not plus alternative ("Not for the margin that price leaves you: that is the dropship server's margin_check"). The agent does not need to infer routing.

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

All Moltline Shipping Maths tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.