Skip to main content
Glama

BRAINIAC Card Payments, SCA & APP Scam Rules

Check EU/US interchange fee caps

card-payments_interchange-cap-check
Read-onlyIdempotent

Compute regulated maximum interchange under EU IFR consumer caps or US Reg II debit caps and flag fees above the cap. Price $0.02 USDC. POST /api/v1/card-payments/interchange-cap-check. An unpaid call returns the x402 payment terms and does not run.

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": {
      "regime": "<regime>",
      "cardType": "<cardType>",
      "amount": "<amount>",
      "currency": "<currency>"
    },
    "name": "card-payments_interchange-cap-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesamount, integer, from 0 to 9007199254740991. Required.
regimeYesregime, string, one of EU_IFR, US_REG_II. Required.
cardTypeYescardType, string, one of consumer_debit, consumer_credit, debit, commercial. Required.
currencyYescurrency, string. Required.
actualFeeNoactualFee, integer, from 0 to 9007199254740991. Optional.
regulatedIssuerNoregulatedIssuer, boolean. Optional.
domesticCapOverrideNodomesticCapOverride, number, from 0 to 1. Optional.
fraudAdjustmentEligibleNofraudAdjustmentEligible, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
capExactNocapExact. Number.
capMinorNocapMinor. Number.
capFormulaNocapFormula. String.
exceedsCapNoexceedsCap. Boolean.
excessMinorNoexcessMinor. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description goes beyond them usefully by disclosing cost ($0.02 USDC), the transport (POST /api/v1/card-payments/interchange-cap-check), and the x402 payment handshake — an unpaid call returns payment terms and does not execute. It stops short of describing error behavior for invalid regime/cardType combinations or what the flagging result looks like, but the output schema covers the latter.

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?

Three sentences, all front-loaded: capability and scope first, then price and endpoint, then the payment-gate behavior. No redundant restatement of the title or schema, and every sentence carries information an agent needs.

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?

For an eight-parameter, output-schema-backed, read-only computation tool, the definition supplies the operational essentials an agent needs before calling: cost, method, path, and the x402 unpaid-call behavior. It is slightly thin on how the optional override/adjustment parameters affect the computation, but the schema and output schema absorb most of that burden.

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 eight parameters are already documented structurally and baseline is 3. The description adds only indirect semantics — by naming 'EU IFR consumer caps' and 'US Reg II debit caps' it hints that regime constrains which cardType values are meaningful — but it never explains actualFee, domesticCapOverride, fraudAdjustmentEligible, or regulatedIssuer.

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 opens with a specific verb and resource: compute the regulated maximum interchange under EU IFR consumer caps or US Reg II debit caps, plus a secondary action to flag fees above the cap. The regulatory scope (EU_IFR vs US_REG_II) makes it unmistakably distinct from the other card-payments_* siblings (pan-check, pan-mask, sca-exemption-evaluate).

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 purpose: you call this when validating whether an assessed interchange fee exceeds the regulatory cap. There is no explicit when-to-use framing against alternatives, no statement of prerequisites such as which regime/cardType pairings are valid, and no guidance on when the optional actualFee or domesticCapOverride should be supplied.

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