Skip to main content
Glama

DataCastle EU Compliance & Customs

datacastle_reconcile_freight_discrepancy

Performs deterministic reconciliation between commercial invoice items and packing list / waybill shipping manifests. Compares line-item quantities, gross/net weights, declared customs values, and flags variances exceeding legal tolerances.

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": {
      "invoiceItems": "<invoiceItems>",
      "shippingItems": "<shippingItems>"
    },
    "name": "datacastle_reconcile_freight_discrepancy"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoiceItemsYesList of items as stated on the commercial invoice.
shippingItemsYesList of items as recorded on the transport waybill or physical packing list.
declaredCurrencyNoISO currency code (e.g. 'EUR', 'SEK', 'USD'). Default: 'EUR'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 behavioral burden. It discloses that reconciliation is deterministic, the fields compared, and that variances exceeding legal tolerances are flagged. It does not explain matching logic, output structure, tolerance sourcing, currency handling, or whether unmatched items are reported, leaving significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core operation, and contains no filler. Every sentence contributes either the reconciliation scope or the comparison and flagging behavior.

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 reconciliation tool with no annotations and no output schema, the description gives a useful behavioral outline but is not complete. It does not describe the expected return shape, how tolerances are determined, how line items are matched, or how currency conversion affects value comparison. These omissions matter because no output schema exists to fill the gap.

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 description coverage is 100%, so the schema fully documents the three parameters. The description refers to invoice items and shipping manifests but adds no extra meaning about parameter shapes, currency behavior, or optionality beyond the schema. This meets the baseline of 3 when the schema does the heavy lifting.

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 states a specific verb and resource: deterministic reconciliation between commercial invoice items and packing list/waybill shipping manifests. It lists the exact comparison fields (quantities, gross/net weights, declared customs values) and the flagging behavior. It does not explicitly distinguish itself from sibling tools such as audit or verification tools, so it falls short of a 5.

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 implies the use case: reconciling freight documentation for variances. However, it gives no explicit when-to-use or when-not-to-use guidance and does not mention alternatives or prerequisites. The implied context is clear enough for a 3 but lacks routing guidance.

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.