Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Validate a US ABA routing number

payment-intelligence_routing-number-validate

Validate a 9-digit US ABA routing number checksum (weights 3-7-1). Bank directory names are not returned in this version. Price $0.02 USDC. POST /api/v1/payment-intelligence/routing-number-validate. Unpaid calls return 402 and do 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": {
      "routingNumber": "<routingNumber>"
    },
    "name": "payment-intelligence_routing-number-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
routingNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does meaningfully: it discloses a per-call price ($0.02 USDC), a hard failure mode ('Unpaid calls return 402 and do not run'), and an output limitation (no bank names). It does not cover idempotency, rate limits, or whether a failed checksum is an error versus a negative result, which keeps it below a 5.

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 with no filler; scope comes first, then the output limitation, then cost and endpoint. The raw 'POST /api/v1/...' path is operationally useful but slightly redundant with the tool name.

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

Completeness3/5

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

For a one-parameter tool with no annotations and no output schema, the description should say what a successful call actually returns (a boolean, a checksum-valid flag, an error object), and it only says what is not returned. Cost and failure-mode disclosure are strong, but the success-path response shape remains undefined.

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 0%, so the description must compensate for the single undocumented parameter. It partially does by specifying the value must be a 9-digit routing number while the schema permits 8–12 characters, which is a useful constraint. It does not clarify whether the input may contain hyphens or spaces, or how the 8–12 schema range relates to the 9-digit rule.

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 ('Validate a 9-digit US ABA routing number checksum') and narrows the scope with '(weights 3-7-1)', which is precise enough that an agent knows this is a pure checksum check rather than a bank lookup. It implicitly distinguishes itself from the IBAN sibling by naming the US ABA domain, but it never explicitly routes to payment-intelligence_iban-validate for non-US input.

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?

Usage is implied by the stated scope (US ABA checksum only) and by the exclusion 'Bank directory names are not returned in this version', which tells the agent not to use it for directory lookups. There is no explicit when-to-use framing, no statement about when to prefer the IBAN validator, and no prerequisite guidance beyond the payment gating.

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