Skip to main content
Glama

BRAINIAC Freight & Customs

Extract a shipping document

freight-customs_shipping-document-extract

Read parties, addresses, goods lines, weights, values, and references from supplied shipment text or a text-based PDF. Fields that are not printed are left empty. Price $0.05 USDC. POST /api/v1/freight-customs/shipping-document-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_shipping-document-extract"
  }
}

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 behavior burden and does well: it states that unprinted fields are returned empty, that the call costs $0.05 USDC, that it is a POST endpoint, and that unpaid calls return 402 and are not executed. Missing details are secondary — no mention of idempotency, size limits, or whether OCR is attempted on non-text PDFs.

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 extraction scope is front-loaded in the first sentence, followed by a data-quality guarantee, then pricing and transport mechanics. Every sentence carries information; only the raw endpoint path is slightly redundant with the tool identity but still useful for error diagnosis.

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?

There is no output schema and no annotations, so the description is the only place return values could be characterized, yet it never says what the response looks like or how extracted fields are keyed. For a complex three-input tool with a deeply nested shipment object and zero schema descriptions, this leaves the agent under-informed about both input roles and result shape.

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 three top-level parameters, one of which is a large nested shipment object with lines, parties, weights, and references, so the description must compensate and largely does not. Listing the extracted field families loosely maps to the shipment object, but the critical ambiguity is unresolved: whether `shipment` supplies known values as hints while `file`/`text` is the source of truth, or how the two input modes combine.

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?

"Read parties, addresses, goods lines, weights, values, and references from supplied shipment text or a text-based PDF" gives a concrete verb and enumerates the extracted entities, which is far more specific than the name alone. It does not distinguish itself from siblings such as freight-customs_bill-of-lading-extract or freight-customs_incoterms-obligation-extract, so the agent must infer the boundary.

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 is implied by the stated inputs: text or a text-based PDF (explicitly excluding scanned/image PDFs, which is a useful implicit constraint). There is no explicit when-to-use versus the specialized extractors in the sibling list, and no stated prerequisite about which inputs to combine.

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