Skip to main content
Glama

BRAINIAC Freight & Customs

Check customs data completeness

freight-customs_data-completeness

List shipment fields that are present or missing in the supplied documents. Duty, restrictions, sanctions, and country-specific requirements stay unverified. Price $0.04 USDC. POST /api/v1/freight-customs/data-completeness. 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_data-completeness"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
shipmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does contribute real context: cost ($0.04 USDC), transport (POST endpoint), and the failure mode that unpaid calls return 402 and do not execute. It stops short of saying what the response contains or what happens when neither file nor text is supplied.

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 purpose, then scope limits, then commercial terms. No filler; each sentence adds information, though the endpoint and price could be compressed.

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 no-annotation, no-output-schema tool with a complex nested input, the description covers purpose, limits, and payment behavior but omits how inputs are combined (file vs text vs shipment) and gives only a one-line implication of the return value. Adequate but with clear gaps.

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 the schema is deeply nested (file with filename/mediaType/fileBase64, free text, and a large shipment object with lines, parties, and totals). The description only gestures at 'supplied documents' and never clarifies the file-vs-text input modes or the optional shipment payload, so it does not compensate for the coverage gap.

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: 'List shipment fields that are present or missing in the supplied documents.' An agent can immediately tell this is a completeness/diagnostics check on documents rather than an extraction or validation tool, though no sibling is named 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 description draws a clear negative boundary ('Duty, restrictions, sanctions, and country-specific requirements stay unverified'), which helps route agents away from using it for compliance checks. However, it gives no positive when-to-use guidance against siblings such as shipment-document-consistency or commercial-invoice-validate, leaving the choice 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