Skip to main content
Glama

BRAINIAC Bank, Credit Union & Charity Registries

Look up an NCUA credit union

registries_ncua-credit-union-lookup
Read-onlyIdempotent

Find a US credit union by NCUA charter number, RSSD id, name, or trade name from the vendored NCUA 5300 Call Report FOICU and TradeNames files. Only credit unions that filed in that cycle are listed. Price $0.03 USDC. POST /api/v1/registries/ncua-credit-union-lookup. 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": "registries_ncua-credit-union-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoname, string, length 2 to 200. Optional.
rssdNorssd, integer, from 1 to 9007199254740991. Optional.
limitNolimit, integer, from 1 to 50. Required.
stateNostate, string. Optional.
charterNocharter, integer, from 1 to 9007199254740991. Optional.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
snapshotNosnapshot. Object.
limitationsNolimitations. Array.
totalCandidatesNototalCandidates. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuinely non-structured facts: the data source files, the filing-cycle coverage limitation, the $0.03 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms instead of running. It does not cover rate limits or result-size behavior beyond the limit parameter.

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 compact sentences, front-loaded with the core lookup capability, followed by coverage caveat, pricing, and payment failure behavior. No redundant or filler wording.

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. Combined with 100% schema coverage and rich annotations, the description covers purpose, data provenance, coverage limits, and payment semantics. Minor gap: it does not mention whether the lookup keys combine as filters or are alternatives, nor any pagination behavior for the limit parameter.

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 the schema already documents all five parameters. The description adds that the identifiers correspond to NCUA charter number and RSSD id and that name and trade name are both searchable, which is modest value over the schema's own field descriptions.

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?

The description names a specific verb and resource ('Find a US credit union'), enumerates the four lookup keys (NCUA charter number, RSSD id, name, trade name), and names the source datasets (NCUA 5300 Call Report FOICU and TradeNames). Siblings registries_fdic-bank-lookup and registries_uk-charity-lookup are distinguishable by the NCUA/US credit union scope stated here.

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?

It gives a clear condition for use (lookup by charter, RSSD, name, or trade name) and a meaningful exclusion: 'Only credit unions that filed in that cycle are listed.' It does not explicitly route the agent to the FDIC or UK charity siblings, so no full when/when-not/alternatives 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