Skip to main content
Glama

BRAINIAC Card Payments, SCA & APP Scam Rules

Parse PSD2 eIDAS certificate roles

card-payments_psd2-certificate-roles
Read-onlyIdempotent

Parse a TPP QWAC/QSealC certificate for PSD2 roles, NCA and authorisation number. Does not verify the chain. Price $0.03 USDC. POST /api/v1/card-payments/psd2-certificate-roles. 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": {
      "certificatePem": "<certificatePem>"
    },
    "name": "card-payments_psd2-certificate-roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
certificatePemYescertificatePem, string, length 32 to 65536. Required.

Output Schema

NameRequiredDescriptionDefault
psd2Nopsd2. Object.
issuerNoissuer. String.
issuesNoissues. Array.
sourcesNosources. Array.
subjectNosubject. String.
notAfterNonotAfter. String.
notBeforeNonotBefore. String.
limitationsNolimitations. Array.
authorisationNoauthorisation. Object.
organizationIdentifierNoorganizationIdentifier. String.

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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description still adds real value beyond them: a price of $0.03 USDC, the POST endpoint, and the critical fact that an unpaid call returns x402 payment terms and does not execute. That payment-gating and non-verification behavior is exactly the context annotations cannot convey.

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, front-loaded sentences: purpose, scope limit, price/endpoint, payment behavior. No filler, no repetition of the title, and the most decision-relevant facts (what it does, what it does not do, cost) come first.

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?

The tool is a simple single-parameter parse with an output schema, so return values need no explanation, and the description covers cost, endpoint, and the chain-verification limit. Only minor gaps remain, such as behavior on malformed or non-TPP certificates, which the output schema may already handle.

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 identifies the payload as a TPP QWAC/QSealC certificate, which adds a little semantic framing over the schema's generic "certificatePem" text, but it offers no encoding, format, or size guidance beyond what the schema already states.

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?

Names a specific verb (Parse) and a precisely scoped resource (TPP QWAC/QSealC eIDAS certificate) and states the extracted fields: PSD2 roles, NCA, authorisation number. That is far more specific than any sibling (pan-check, pan-mask, sca-exemption-evaluate), so an agent can route without opening the schema.

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 supplies one useful exclusion ("Does not verify the chain"), which implies when the tool is appropriate for pure field extraction. However, it never says when to prefer it, what prerequisites exist, or what to do for chain validation; 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