Skip to main content
Glama

Triplicate – export documents

Check a container or B/L number

check_container_number
Read-only

Use when a user wants to track a container, bill of lading or booking number, or to know whether a container number is valid. Check a shipping container number (ISO 6346 check digit), find who owns its prefix (shipping line or container leasing company, e.g. MSCU = MSC, TGHU = Textainer) and get the line's official tracking page. Bill of lading numbers are recognised by the carrier's B/L prefix, usually its SCAC (e.g. HLCU, COSU; MSC uses MEDU, while its SCAC is MSCU). Does not return live status: the line's own site shows it.

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": {
      "number": "<number>"
    },
    "name": "check_container_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesContainer number, e.g. 'MSCU1234566' (4 letters + 7 digits), or a bill of lading / booking number, e.g. 'MEDUAB123456'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's job is to add scope, which it does by stating what is returned (prefix owner, carrier tracking URL) and what is not (live status). The openWorldHint=false claim sits slightly at odds with handing out external tracking pages, but the description resolves this by being clear it only returns a link, not live data. No mention of failure behavior for invalid check digits or unrecognised prefixes.

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-loaded with the trigger, then the capability, then the limitations; every sentence carries information. The middle enumeration is somewhat dense in a single long sentence, but nothing is padding or restatement of the name.

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 one-parameter read-only lookup with no output schema, the description covers what goes in, what comes out (validation result, prefix owner, tracking URL) and the main limitation. It stops short of describing the shape of a failed validation or the exact fields returned, which would be the remaining gap.

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 the baseline is 3, but the description earns above it by explaining that the single 'number' parameter accepts two semantically different inputs and by decoding the prefix rules, including the non-obvious nuance that MSC's containers use MSCU while its B/Ls use MEDU despite its SCAC being MSCU. That is meaning the schema examples alone do not convey.

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?

Specific verb+resource with the full scope spelled out: validates a container number (ISO 6346 check digit), resolves prefix ownership (MSCU = MSC, TGHU = Textainer), and returns the carrier's tracking page, plus handling of B/L and booking numbers. An agent can tell exactly what comes back and that it differs from the trade-document siblings, none of which deal with container/B/L number validation.

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 wants to track a container, bill of lading or booking number, or to know whether a container number is valid') and closes with an explicit exclusion ('Does not return live status: the line's own site shows it'), which tells the agent when to redirect the user rather than call again.

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