Skip to main content
Glama

eu_cash_payment_limit_audit

Read-onlyIdempotent

[Pan-European cash payment limit audit. Deterministic calculation, read-only, side-effect free]. Enforces the mandatory €10,000 pan-EU cash limit under Regulation (EU) 2024/1624 Article 80 and stricter national ceilings (Italy €5k, France/Spain €1k), detecting artificial installment smurfing. Usage: Pass transaction amount, country, and residential status to assess legal validity of physical cash settlement. Returns: JSON object with { countryIso2: string, totalCashAmountEur: number, applicableCeilingEur: number, isPaymentPermitted: boolean, isCeilingExceeded: boolean, linkedTransactionsSmurfingDetected: boolean, sanctionsRisk: object }.

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": {
      "countryIso2": "<countryIso2>",
      "isTraderInGoodsOrServices": "<isTraderInGoodsOrServices>",
      "isCustomerResidentInCountry": "<isCustomerResidentInCountry>",
      "transactions": "<transactions>"
    },
    "name": "eu_cash_payment_limit_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryIso2Yes2-letter EU country code where the commercial transaction takes place
transactionsYesSingle transaction or series of linked cash payments within a 30-day window
isTraderInGoodsOrServicesYesWhether payment is made to a person trading in goods or providing services
isCustomerResidentInCountryYesWhether paying customer has tax residence in the transaction country

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'Deterministic calculation, read-only, side-effect free' rather than contradicting it. It adds genuinely new behavioral context: which national ceilings apply, a 30-day linked-transaction window, smurfing detection, and a sanctions-risk output, though it doesn't mention any permission or rate-limit constraints.

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?

Front-loaded purpose, then clearly delimited 'Usage' and 'Returns' blocks with no filler. The single dense bracketed first sentence is the only mild structural weakness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps in to enumerate the returned JSON fields, which is exactly what an agent needs to parse results. It is slightly incomplete in describing inputs, since the mandatory trader-in-goods-or-services flag is never mentioned, but the tool's overall contract is clear.

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 parameters are already fully documented and the baseline is 3. The description adds interpretive value by tying countryIso2 to national ceilings and the transaction list to a 30-day smurfing window, but its usage line is imprecise: it says to pass 'amount, country, and residential status' while omitting the required isTraderInGoodsOrServices flag and recasting the transactions array as a single amount.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ('Pan-European cash payment limit audit') and anchors it to a named legal basis (Regulation (EU) 2024/1624 Article 80) plus concrete national ceilings. No sibling covers cash-payment ceilings, so an agent can distinguish this tool immediately.

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

Usage Guidelines4/5

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

The 'Usage' line gives clear context: use it to assess legal validity of a physical cash settlement by passing amount, country and residency. It stops short of stating when NOT to use it or pointing to any alternative tool, so it does not reach the top band.

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