Skip to main content
Glama

BRAINIAC Freight & Customs

Validate a packing list

freight-customs_packing-list-validate

Check package counts and net and gross weights on a supplied packing list. A missing weight is not treated as zero. Price $0.04 USDC. POST /api/v1/freight-customs/packing-list-validate. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "freight-customs_packing-list-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
shipmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that missing weights are not treated as zero, that the call costs $0.04 USDC, and that unpaid calls return 402 without running, but it omits other relevant behavior such as whether validation is read-only, what kind of result or error is produced, and any authentication or rate-limit context.

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?

The purpose is front-loaded, followed by useful behavioral constraints and billing information. The endpoint path is somewhat redundant for an MCP tool, but the description remains short and readable overall.

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

Completeness2/5

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

For a tool with three complex inputs, no annotations, no output schema, and zero schema description coverage, the description is incomplete. It explains what is checked and some payment behavior, but leaves the agent without guidance on how to supply the packing list, how to use the shipment object, or what a successful validation response contains.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must explain the three top-level inputs. It only says the packing list is 'supplied' and never explains the file, text, or shipment parameters, nor how they relate to one another, despite the shipment object being deeply nested and complex.

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 uses a specific verb and resource: check package counts and net/gross weights on a packing list. It is clearly narrower than a generic document extractor or invoice validator, but it does not explicitly differentiate itself from sibling tools such as freight-customs_shipment-weight-volume-calculate or freight-customs_commercial-invoice-validate.

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 description implies the tool is used when a packing list needs package-count and weight validation, but it gives no explicit when-to-use or when-not-to-use guidance relative to the many sibling validation and extraction tools. Alternatives are neither named nor excluded.

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