Skip to main content
Glama

BRAINIAC KYC National Identifier Checks

Validate national ID formats

kyc-identifiers_national-id-validate
Read-onlyIdempotent

Format and checksum checks for GB NINO, US SSN and PL PESEL. Does not confirm issuance or identity. Price $0.01 USDC. POST /api/v1/kyc-identifiers/national-id-validate. 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>",
      "value": "<value>"
    },
    "name": "kyc-identifiers_national-id-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesvalue, string, length 1 to 20. Required.
schemeYesscheme, string, one of GB_NINO, US_SSN, PL_PESEL. Required.

Output Schema

NameRequiredDescriptionDefault
flagsNoflags. Array.
validNovalid. Boolean.
checksNochecks. Array.
schemeNoscheme. String.
derivedNoderived. Object.
sourcesNosources. Array.
normalisedNonormalised. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the cost ($0.01 USDC), the payment protocol behavior (an unpaid call returns x402 terms and does not execute), and the underlying endpoint. The read-only, idempotent nature is already covered by annotations, so the added payment-gating detail is the genuinely valuable disclosure here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short, front-loaded sentences: scope first, limitation second, price and endpoint after. The raw endpoint path is marginal information, but the price and payment-gating sentences clearly earn their space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter validation tool with full schema coverage, complete annotations, and an output schema, the description covers everything an agent needs: what is validated, what it does not assert, what it costs, and what happens without payment.

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% and the scheme enum is fully enumerated in the schema, so the description's mention of the three schemes adds little beyond structured data. With no additional detail on the 'value' parameter's expected formatting per scheme, this sits at the baseline.

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 operation (format and checksum checks) on a specific resource (national ID numbers) and enumerates the exact schemes covered: GB NINO, US SSN, PL PESEL. The second sentence bounds the result precisely with 'Does not confirm issuance or identity,' so an agent knows the tool validates syntax, not legitimacy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear negative scope ('does not confirm issuance or identity') that tells an agent when this tool's output is insufficient, and the payment note explains what happens on an unpaid call. No sibling tools exist to route against, so the absence of an explicit alternative is not a real gap.

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