Skip to main content
Glama

Credit Union Directory

credit_unions
Read-onlyIdempotent

Directory of NCUA-insured credit unions. (Source: NCUA.) Dollar amounts are in thousands of US dollars ($000s): NCUA files the 5300 in whole dollars and this API divides by 1,000 so credit unions read like banks. Ratios are percentages.

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": "credit_unions"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName or NCUA charter number, case-insensitive. Matches any part of the legal name; when that finds nothing, falls back to the site's name matcher, which forgives punctuation, spacing and common abbreviations.
stateNoTwo-letter state filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description then adds genuinely non-obvious behavioral context that annotations cannot: dollar amounts are scaled to thousands ($000s) and ratios are expressed as percentages — a critical detail that would otherwise cause a 1,000x misreading of returned figures. It stops short of describing result caps or pagination.

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?

Front-loads the purpose in the first five words, then attaches the source and the unit conventions. No filler, though the '($000s)' and 'divides by 1,000' phrasing is somewhat redundant with 'Dollar amounts are in thousands'.

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?

For a zero-required-parameter, read-only directory with no output schema, the definition covers source, scope, and the unit conventions an agent most needs to interpret results correctly. It does not describe which fields are returned or whether the result set is bounded, which is the main remaining gap given the absence of an output schema.

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 schema itself fully documents both 'q' (name or charter number, case-insensitive, partial match, with fuzzy fallback) and 'state' (two-letter filter). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

Names a specific resource ('Directory of NCUA-insured credit unions') with a clear source attribution (NCUA), so an agent knows this is a lookup/list of credit unions rather than branches, trends, or a single profile. It does not, however, explicitly distinguish itself from near-siblings like 'credit_union' (singular) or 'cu_branches', leaving the agent to infer that this is the institution-level list.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all — nothing tells the agent to prefer this over 'credit_union' for a single lookup or over 'credit_union_trends' for time series. Usage is only implied by the word 'Directory'.

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