Skip to main content
Glama

BRAINIAC Card Payments, SCA & APP Scam Rules

Validate a card PAN (Luhn)

card-payments_pan-check
Read-onlyIdempotent

Check card number length and Luhn check digit. Never echoes the full PAN; returns masked form and last4 only. Price $0.01 USDC. POST /api/v1/card-payments/pan-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": {
      "pan": "<pan>"
    },
    "name": "card-payments_pan-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
panYespan, string, length 12 to 32. Required.

Output Schema

NameRequiredDescriptionDefault
last4Nolast4. String.
lengthNolength. Number.
maskedNomasked. String.
sourcesNosources. Array.
luhnValidNoluhnValid. Boolean.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses privacy behavior (never echoes the full PAN, returns masked form and last4), the endpoint, the $0.01 USDC price, and crucially that an unpaid call returns x402 payment terms and does not execute. These are material operational details an agent needs before invoking the tool.

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?

Four short sentences, each carrying distinct information: validation scope, privacy return behavior, payment cost, and the unpaid x402 failure path. Nothing is redundant and the critical validation purpose is front-loaded.

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 explained in detail, and the description still adds the masked/last4 privacy contract. Payment and failure behavior are covered; the only minor gap is explicit routing versus sibling tools.

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 coverage is 100% and the single pan parameter is fully documented with type, length bounds, and required status. The description adds only the privacy implication of the PAN input, not additional syntax or format guidance beyond the schema; baseline 3 is appropriate.

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: check card number length and Luhn check digit. It is clearly distinguishable from masking or exemption siblings because it describes validation semantics and explicitly notes the masked return form.

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 usage via the validation scope and the payment requirement, but it does not explicitly say when to call this versus card-payments_pan-mask or which downstream checks should precede or follow it. Adequate context, but no exclusions or named alternatives.

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