Skip to main content
Glama

BRAINIAC Bank Account Identifiers & Payment Files

UK sort code + account modulus check

bank-payments_uk-modulus-check
Read-onlyIdempotent

Check whether a UK sort code and account number pair can be valid using Vocalink modulus weights (valacdos/scsubtab) and exceptions 1–14. Price $0.02 USDC. POST /api/v1/bank-payments/uk-modulus-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": {
      "sortCode": "<sortCode>",
      "accountNumber": "<accountNumber>"
    },
    "name": "bank-payments_uk-modulus-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortCodeYessortCode, string, length 6 to 12. Required.
accountNumberYesaccountNumber, string, length 6 to 14. Required.

Output Schema

NameRequiredDescriptionDefault
validNovalid. Boolean.
checksNochecks. Array.
resultNoresult. String.
sourcesNosources. Array.
sortCodeNosortCode. String.
limitationsNolimitations. Array.
specVersionNospecVersion. String.
accountNumberNoaccountNumber. String.
checksAvailableNochecksAvailable. Boolean.
standardisedSortCodeNostandardisedSortCode. String.
standardisedAccountNumberNostandardisedAccountNumber. String.

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, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: a fixed price of $0.02 USDC, the POST route, and critically that an unpaid call returns x402 payment terms instead of executing — a payment-gating behavior an agent must know before calling. It could still say more about what a pass/fail response implies.

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 what the tool does, then cost/endpoint, then the failure-mode note. No filler, no restated title, and the payment caveat sits last where it cannot be missed.

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, and annotations cover the safety profile; the description closes the remaining gap by disclosing the payment requirement and unpaid-call behavior. Minor residual gap: it does not distinguish a modulus failure from an input-format rejection, nor mention validation type (modulus 10/11) results explicitly.

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% with both required params documented including length bounds, so the schema carries the load. The description adds the useful semantic that the two fields are treated as a pair validated by Vocalink modulus weights, but gives no format guidance (digit-only, leading zeros, sort code formatting) beyond what the schema 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?

States a specific verb ('Check') plus the exact resource (UK sort code / account number pair) and names the underlying algorithm (Vocalink modulus weights, valacdos/scsubtab, exceptions 1–14). The scope limit is baked in with 'can be valid', so an agent knows this is a modulus-range check rather than full account verification, and it cannot be confused with any sibling (IBAN, BACS, SEPA, NACHA, UETR tools).

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 purpose makes the natural use case evident, and the payment note implies the call must be funded before it produces a result. However, there is no explicit when-to-use/when-not guidance — nothing says to pair it with a format check first, or what an agent should do when the check passes versus fails.

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