Skip to main content
Glama

BRAINIAC Freight & Customs

Cross-check shipment documents

freight-customs_shipment-document-consistency

Compare references, parties, quantities, and weights across at least two supplied documents. A field that appears on only one document is reported separately from a conflict. Price $0.06 USDC. POST /api/v1/freight-customs/shipment-document-consistency. 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_shipment-document-consistency"
  }
}

Input Schema

NameRequiredDescriptionDefault
packingListNo
billOfLadingNo
commercialInvoiceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose notable traits: the $0.06 USDC charge, the POST endpoint, and that unpaid calls return 402 without executing. It also explains the output distinction between a one-sided field and a true conflict, but it omits what happens if fewer than two documents are supplied and whether each document is passed as a file, raw text, or structured shipment object.

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 sentences, front-loaded with the action and the conflict-vs-missing-field distinction. The endpoint and pricing lines are utilitarian but compact; nothing is padded.

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

Completeness3/5

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

For a tool with a deeply nested three-document schema and no output schema, the definition covers the core behavior and the payment failure mode. It is thin on how each document should be supplied and on what the response actually contains beyond the conflict/missing split, which an agent needs before constructing a large payload.

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 description coverage is 0% across a large nested schema with three document objects, so the description must compensate. It partially does by naming the compared domains and implying at least two of the document params must be filled, but it never explains the file-vs-text-vs-shipment alternatives inside each document object.

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 opens with a specific verb and comparison fields (references, parties, quantities, weights) across documents, which is clearly distinct from extraction or single-document validation. It stops short of naming the sibling tools that would be the fallback when only one document is on hand, so recognition is clear but routing is not stated.

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 phrase 'across at least two supplied documents' gives a real precondition, which is more than most definitions offer. It never says which tool to use instead when only one document exists (e.g., the packing-list or commercial-invoice validators), so usage is implied rather than directed.

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