Skip to main content
Glama

BRAINIAC Freight & Customs

Validate a commercial invoice

freight-customs_commercial-invoice-validate

Check that supplied invoice lines, quantities, and amounts agree, and that the seller, buyer, currency, and total are present. No duty is calculated. Price $0.05 USDC. POST /api/v1/freight-customs/commercial-invoice-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_commercial-invoice-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
shipmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full load, and it discloses the paid-call economics ($0.05 USDC), the payment gate ('Unpaid calls return 402 and do not run'), the transport (POST endpoint), and the scope limit that no duty is computed. It still does not say whether a failing invoice returns a findings list or raises an error, nor whether invalid input is rejected or reported.

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-loads the validation intent in one sentence, then adds short scope, price, endpoint, and payment-gate sentences with no filler. Slightly fragmented by the bare endpoint and price lines, but each carries actionable information an agent needs before calling.

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 a large nested schema, zero schema coverage, no annotations, and no output schema, the description under-serves the two things an agent most needs: how to choose between file and text input and how validation failures are surfaced. The billing and no-duty notes are good, but input-mode and result-shape gaps are substantial for this complexity.

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 a deeply nested three-parameter object, so the description must compensate and largely does not. It hints that quantities/amounts (shipment.lines) and seller/buyer/currency/total (shipment.parties, currency, totalAmount) are examined, but it never explains the file-versus-text-versus-shipment modes, that all top-level parameters are optional, or what a caller must minimally provide.

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?

States a specific verb and resource ('Check that supplied invoice lines... agree') and enumerates the concrete fields validated: lines, quantities, amounts, seller, buyer, currency, total. 'No duty is calculated' bounds the scope. The invoice-specific field list implicitly separates it from packing-list-validate and document-consistency, though no sibling is named.

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?

Usage context is implied by the field list and the exclusion of duty calculation, letting an agent infer this is a pre-declaration invoice sanity check. However there is no explicit when-to-use versus siblings like packing-list-validate or shipment-document-consistency, and no stated prerequisite about which of file/text/shipment must be supplied.

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