Skip to main content
Glama

BRAINIAC Card Payments, SCA & APP Scam Rules

Evaluate PSD2 SCA exemptions

card-payments_sca-exemption-evaluate
Read-onlyIdempotent

Decide which PSD2 RTS SCA exemptions may apply to a remote or contactless payment from caller-supplied facts. Price $0.03 USDC. POST /api/v1/card-payments/sca-exemption-evaluate. 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": {
      "channel": "<channel>",
      "instrument": "<instrument>",
      "amountEur": "<amountEur>"
    },
    "name": "card-payments_sca-exemption-evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
traNotra, object. Optional.
channelYeschannel, string, one of remote, contactless_pos. Required.
amountEurYesamountEur, number, from 0 to any. Required.
instrumentYesinstrument, string, one of card, credit_transfer. Required.
sinceLastScaNosinceLastSca, object. Required.
firstInSeriesNofirstInSeries, boolean. Required.
sameOwnerSameAspspNosameOwnerSameAspsp, boolean. Required.
trustedBeneficiaryNotrustedBeneficiary, boolean. Required.
recurringSameAmountSamePayeeNorecurringSameAmountSamePayee, boolean. Required.
trustedBeneficiaryListChangingNotrustedBeneficiaryListChanging, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
evaluatedNoevaluated. Array.
exemptionsNoexemptions. Array.
limitationsNolimitations. Array.
scaRequiredNoscaRequired. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses pricing ($0.03 USDC), the transport (POST /api/v1/card-payments/sca-exemption-evaluate), and the important gating behavior that an unpaid call returns x402 payment terms and does not execute. That payment-gate detail is genuinely useful context the annotations do not carry; it stops short of describing latency or output shape, which is acceptable since an output schema exists.

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 short sentences, each earning its place: purpose first, then price and endpoint, then the failure mode. No redundancy and nothing buried.

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 a 10-parameter, nested-schema tool with an output schema and rich annotations, the description covers the essentials: what is decided, the call mechanics, and the payment gate. It could say slightly more about the domain inputs (e.g. that TRA and sinceLastSca facts drive the decision), but nothing an agent needs in order to invoke it correctly is missing.

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 already documents all 10 parameters including the nested tra and sinceLastSca objects and the two enums. The description adds no parameter-level meaning beyond the schema, 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?

States a specific verb and resource: decide which PSD2 RTS SCA exemptions may apply, scoped to remote or contactless payments from caller-supplied facts. That is precise enough for an agent to distinguish it from the sibling tools (certificate roles, scam reimbursement, interchange cap, PAN check/mask), none of which evaluate exemptions, though it never names or contrasts them 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?

Usage is implied by the purpose line ('from caller-supplied facts') and by the payment-gating note, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent can infer the context but is not told what facts are required versus optional.

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