Skip to main content
Glama

BRAINIAC Card Payments, SCA & APP Scam Rules

UK APP scam reimbursement split

card-payments_app-scam-reimbursement
Read-onlyIdempotent

Calculate the UK mandatory APP scam reimbursement amount and 50:50 receiving-PSP contributions under PSR rules. Price $0.03 USDC. POST /api/v1/card-payments/app-scam-reimbursement. 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": {
      "scheme": "<scheme>",
      "payments": "<payments>",
      "claimDate": "<claimDate>"
    },
    "name": "card-payments_app-scam-reimbursement"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemeYesscheme, string, one of FPS, CHAPS. Required.
paymentsYespayments, array. Required.
claimDateYesclaimDate, string. Required.
vulnerableNovulnerable, boolean. Required.
excessAppliedNoexcessApplied, integer, from 0 to 10000. Required.
exceptionsAssertedNoexceptionsAsserted, array. Required.

Output Schema

NameRequiredDescriptionDefault
notesNonotes. Array.
excessNoexcess. Number.
sourcesNosources. Array.
eligibleNoeligible. Boolean.
claimValueNoclaimValue. Number.
cappedValueNocappedValue. Number.
limitationsNolimitations. Array.
receivingPspSharesNoreceivingPspShares. Array.
requiredReimbursementNorequiredReimbursement. Number.

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, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the $0.03 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing — critical for an agent that might otherwise treat a payment-required response as a result.

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, front-loaded with the purpose, then cost, then transport and payment-gate behavior. No repeated or filler content, and each 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?

An output schema exists, so return values need not be described, and annotations plus the schema cover safety and inputs. The description supplies cost, endpoint and failure-mode behavior; the only mild gap is that no domain semantics are given for the conditional fields (vulnerable, excessApplied, exceptionsAsserted) that materially change the calculation.

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 all six parameters are documented in the schema and the baseline is 3. The description does not add domain meaning for fields like 'vulnerable', 'excessApplied', or 'exceptionsAsserted' beyond what the schema states, though the phrase '50:50 receiving-PSP contributions' loosely maps to receivingPsp.

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?

States a specific verb and resource: 'Calculate the UK mandatory APP scam reimbursement amount and 50:50 receiving-PSP contributions under PSR rules.' This names the computation, the regulatory basis (PSR), and the two outputs (reimbursement amount, PSP split), which none of the sibling card-payments tools cover.

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 domain is narrow enough that the when-to-use case is implied by the calculation described, and no sibling tool overlaps. However, there is no explicit statement of prerequisites, exclusions, or conditions (e.g. that the claim must fall under PSR APP scam scope) that would tell an agent when this is the wrong tool.

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