Skip to main content
Glama

BRAINIAC Freight & Customs

Prepare a customs evidence report

freight-customs_preparation-report

Combine document checks, weight evidence, the named Incoterm, and UK Trade Tariff candidates. No declaration is submitted and no shipment is booked. Price $0.12 USDC. POST /api/v1/freight-customs/preparation-report. 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_preparation-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagesNo
shipmentNo
packingListNo
billOfLadingNo
commercialInvoiceNo
volumetricDivisorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 burden, and it does disclose real behavior: it is non-mutating with respect to customs and booking, costs $0.12 USDC, and unpaid calls return 402 without running. It omits anything about what the returned report contains, partial-failure behavior, or whether all six payload sections are optional.

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?

Four short, front-loaded sentences with no filler; scope comes first and the transaction mechanics last. The raw URL and price could arguably be trimmed, but each sentence carries distinct information.

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?

This is a heavy nested payload with no output schema, no annotations, and zero schema descriptions, so the description is the only guidance the agent has. It leaves the agent unable to tell how to supply each document (base64 file, extracted text, or structured shipment), what the report returns, or which fields drive the result.

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

Parameters2/5

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

Schema description coverage is 0% across six deeply nested parameters, so the description must compensate and largely does not. It hints that packing list, bill of lading, commercial invoice and shipment data are expected, but never explains the file-vs-text-vs-shipment alternatives inside each document object, nor mentions volumetricDivisor at all.

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 first sentence names a specific verb ("Combine") and enumerates the evidence classes being aggregated: document checks, weight evidence, Incoterm, and UK Trade Tariff candidates. That makes it clearly the aggregation/report step rather than a single-document validator like its siblings, though it never says so explicitly.

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 second sentence rules out the obvious wrong uses (no declaration submitted, no booking), which is genuinely useful scope guidance. However, it gives no positive trigger for choosing this over freight-customs_shipment-document-consistency or the individual extract/validate tools, and no statement of prerequisites.

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