Skip to main content
Glama

BRAINIAC Card Payments, SCA & APP Scam Rules

Mask a PAN or redact PANs in text

card-payments_pan-mask
Read-onlyIdempotent

PCI DSS display masking for a single PAN, or find and redact Luhn-valid PANs in free text. Price $0.01 USDC. POST /api/v1/card-payments/pan-mask. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "card-payments_pan-mask"
  }
}

Input Schema

NameRequiredDescriptionDefault
panNopan, string, length 12 to 32. Optional.
textNotext, string, length 0 to 1048576. Optional.
binLengthNobinLength, value. Required.

Output Schema

NameRequiredDescriptionDefault
maskedNomasked. String.
sourcesNosources. Array.
limitationsNolimitations. Array.

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 (which already declare read-only, idempotent, non-destructive, open-world), the description discloses the cost ($0.01 USDC), the transport endpoint, and — critically — that an unpaid call returns x402 payment terms and does not execute. That payment-gate failure mode is behavior an agent cannot get from annotations or schema; only the response payload is left unexplained.

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, front-loaded sentences: capability first, then cost and endpoint, then the payment-gate caveat. No redundant restatement of the title or schema, and every sentence carries operational information.

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-value explanation is not needed, and the description covers both input modes plus the payment prerequisite. Remaining gap is minor: it doesn't clarify the binLength effect or mutual exclusivity of pan/text, though the schema documents both fields.

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 baseline is 3. The description adds mode-level meaning by pairing 'pan' with single-value masking and 'text' with free-text redaction, but says nothing about binLength (6 vs. 8) or what happens when both pan and text are supplied.

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 ('PCI DSS display masking for a single PAN', 'find and redact Luhn-valid PANs in free text'), making the two operating modes clear. It does not explicitly name or contrast with sibling tools such as card-payments_pan-check, so the agent must infer the boundary, but the purpose itself is unambiguous.

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 two modes (single PAN vs. free-text redaction) are described, which implicitly tells the agent which input to supply, but there is no explicit when-to-use/when-not-to-use guidance and no reference to alternatives like pan-check for validation-only needs. Usage must be inferred from the purpose statement.

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