Maglev Parts

Estimate US landed cost

landed_cost

Read-only

Estimate US landed cost for a part in the Maglev catalog. Needs its catalog id: find it with search_parts first; parts outside the catalog cannot be priced here. Returns goods value + duty stack for the origin (MFN, Section 301, other programs, each with a source) + merchandise processing fee + freight. An estimate, not customs advice.

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

Input Schema

Name	Required	Description
`id`	Yes
`qty`	No
`origin`	No	ISO-2 country it ships from; defaults to the part's origin
`unit_usd`	No	Unit price to use when the part has no listed price
`freight_usd`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is already covered; the description adds the important caveat that this is an estimate rather than customs advice. It also enumerates the return composition (goods value, duty stack with sources, MPF, freight), which is valuable given there is no output schema. It does not state whether duty rates are cached or refreshed, which keeps it short of a 5.

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?

Four compact sentences, front-loaded with purpose, then prerequisite, then return contents, then disclaimer. Every sentence carries distinct information, including the useful "find it with search_parts first" routing hint.

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?

With no output schema, the description does the heavy lifting by describing the returned cost components, and it covers the main prerequisite and exclusion. It falls short on the three optional monetary/quantity inputs, whose effect on the estimate is unstated.

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 coverage is 40% and the description explains the key input (catalog id, obtainable via search_parts) and that origin drives the duty stack. However, qty, unit_usd, and freight_usd inputs get no explanation beyond the schema, and nothing says whether qty affects duty tiering. The description compensates only partially for the coverage gap.

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 and resource: "Estimate US landed cost for a part in the Maglev catalog." An agent can immediately distinguish this from siblings like get_quotes or build_rfq, which do different jobs.

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?

Gives both the precondition ("Needs its catalog id: find it with search_parts first") and an explicit exclusion ("parts outside the catalog cannot be priced here"). It names the sibling to use for the prerequisite step, so no inference is needed.

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

All Maglev Parts 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.

Resources

Need Help?