Skip to main content
Glama

BRAINIAC Tariffs & Trade Reference

Validate ISO 6346 container number

trade-tariff_container-iso6346-validate
Read-onlyIdempotent

Validate freight container owner code, category identifier, serial, and ISO 6346 check digit. Does not confirm registration. Price $0.01 USDC. POST /api/v1/trade-tariff/container-iso6346-validate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "containerNumber": "<containerNumber>"
    },
    "name": "trade-tariff_container-iso6346-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
containerNumberYescontainerNumber, string, length 10 to 15. Required.

Output Schema

NameRequiredDescriptionDefault
validNovalid. Boolean.
sourcesNosources. Array.
formatOkNoformatOk. Boolean.
ownerCodeNoownerCode. String.
checksumOkNochecksumOk. Boolean.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
serialNumberNoserialNumber. String.
containerNumberNocontainerNumber. String.
categoryIdentifierNocategoryIdentifier. String.
expectedCheckDigitNoexpectedCheckDigit. Number.
observedCheckDigitNoobservedCheckDigit. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/destructive annotations by disclosing the commercial gate: a $0.01 USDC charge on POST /api/v1/trade-tariff/container-iso6346-validate, and critically that an unpaid call returns x402 payment terms and does not execute. That failure mode is exactly the kind of behavioral trait an agent must know before calling.

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?

Three tight sentences: capability first, scope limit second, cost and failure mode last. Every sentence carries distinct information with no repetition of the title or schema.

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?

Annotations cover safety and an output schema covers return values, so the description only needed to add the payment and scope context — which it does. Minor gap: it does not say whether an invalid container number yields an error or a negative result payload.

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% (one required string, length 10-15), so the baseline would be 3. The description adds real meaning by explaining what the string is decomposed into (owner code, category identifier, serial, check digit), which helps the agent understand valid input formats beyond the bare min/max length.

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 (validate) plus the exact resource and format (ISO 6346 container number), and enumerates the sub-components checked (owner code, category identifier, serial, check digit). No sibling tool in the catalog touches container numbers, so no differentiation statement is needed.

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?

"Does not confirm registration" is a useful scope caveat that tells the agent not to rely on this for registry verification, but there is no explicit when-to-use guidance or routing to an alternative tool. Usage is implied rather than stated.

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