Skip to main content
Glama

DataCastle EU Compliance & Customs

datacastle_audit_customs_document

Performs deep audit and entity extraction on EU freight and customs documents (CMR Consignment Notes, Tullverket SAD Customs Declarations, Commercial Invoices). Extracts TARIC/HS codes, gross/net weights, Incoterms, currency, and cross-checks for discrepancy risks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "documentText": "<documentText>"
    },
    "name": "datacastle_audit_customs_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentTextYesRaw text content of the customs document, CMR note, or commercial invoice to audit.
documentTypeNoType of document. Options: 'CMR', 'SAD_DECLARATION', 'COMMERCIAL_INVOICE', 'AUTO_DETECT'. Defaults to 'AUTO_DETECT'.

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 carries the full burden. It discloses the substantive behavior beyond the name: entity extraction targets and that it cross-checks for discrepancy risks. However it does not state that the operation is read-only/non-mutating, whether documents are stored, auth or rate-limit requirements, or what the audit produces — relevant for a tool whose name implies data handling.

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?

Two dense sentences with no filler, front-loaded with the action and scope before the extraction detail. Slightly term-heavy but every clause carries information.

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?

There is no output schema, so the description should convey what a caller gets back; it only implies results via 'extracts ... and cross-checks,' without stating the return structure, whether flags/scores are included, or how uncertainty is reported. Acceptable for a two-parameter tool, but incomplete for a document-audit operation expected to produce structured findings.

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 coverage is 100% and both parameters, including the documentType enum, are fully documented in the schema. The description adds only domain mapping (CMR/SAD/Commercial Invoice correspond to the enum values) and no syntax, size limits, or format expectations for documentText beyond the schema entry, so the baseline 3 applies.

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?

Uses a specific verb+resource pair ('deep audit and entity extraction on EU freight and customs documents') and enumerates named document families (CMR Consignment Notes, Tullverket SAD Declarations, Commercial Invoices) plus extracted fields (TARIC/HS codes, weights, Incoterms, currency). An agent can tell what it does, but it never names or distinguishes itself from siblings like datacastle_reconcile_freight_discrepancy or datacastle_verify_taric_code, despite overlapping 'discrepancy risk' language.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use / when-not-to-use guidance and no prerequisites are stated. The scope ('EU freight and customs documents') implies the use case, but nothing tells the agent why to pick this over the reconciliation or TARIC-verification siblings that cover adjacent needs.

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.