Skip to main content
Glama

BRAINIAC Freight & Customs

Extract a bill of lading

freight-customs_bill-of-lading-extract

Read the bill of lading number, shipper, consignee, container, and weight from supplied text. No shipment is booked. Price $0.05 USDC. POST /api/v1/freight-customs/bill-of-lading-extract. 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_bill-of-lading-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
shipmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose real behavioral traits: a $0.05 USDC cost, the concrete endpoint, and the failure mode that unpaid calls return 402 without running. It omits what the response looks like and any limits on input size or throughput, which keeps it short of a 5.

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 what is read and immediately followed by the non-side-effect and payment facts. No filler, though the endpoint string is arguably redundant for an agent that already knows the tool name.

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 schema, zero annotation coverage, no output schema, and zero required parameters, the description covers purpose, cost, and payment failure but leaves the input contract largely unexplained. An agent would still not know whether to send text, a file, structured shipment data, or several at once.

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% and there are three top-level parameters, two of them nested objects (file, shipment). The description only gestures at the 'text' input and lists some extracted fields; it never explains the file parameter, the mediaType/fileBase64 requirements, or the large shipment object with its parties and lines sub-structures.

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 gives a specific verb and resource ('Read the bill of lading number, shipper, consignee, container, and weight from supplied text') and scopes the output fields, which is much clearer than the bare title. It does not differentiate itself from the sibling freight-customs_shipping-document-extract, which an agent could plausibly choose for the same input.

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?

'from supplied text' and 'No shipment is booked' imply the extraction-only context and rule out a booking side effect, and the 402 note tells the agent payment must be settled first. However, there is no explicit statement of when to pick this over shipping-document-extract or commercial-invoice-validate, so the routing decision is left to inference.

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