Skip to main content
Glama

Credit Union Snapshot

credit_union
Read-onlyIdempotent

Latest snapshot for one credit union. (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

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": {
      "cu_number": "<cu_number>"
    },
    "name": "credit_union"
  }
}

Input Schema

NameRequiredDescriptionDefault
cu_numberYesNCUA charter number.

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?

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot carry: the unit convention ($000s), why it differs from NCUA's raw 5300 filing, and that ratios are percentages — all directly relevant to interpreting the result. It does not mention freshness/staleness beyond 'latest' or any data-availability caveats.

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 sentences, front-loaded with the core purpose, followed by source attribution and unit conventions. Each sentence carries information; the parenthetical explanation of NCUA's whole-dollar filing is slightly verbose but justifies itself by preventing a 1000x misread.

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, read-only tool the calling mechanics are fully covered, and the units/ratio conventions are a strong addition. However, with no output schema, the agent gets no sense of what the snapshot contains (financial statement sections, fields, period granularity, whether missing institutions error or return empty), leaving a real gap for a data-returning tool.

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 single parameter cu_number is documented as an NCUA charter number with an example, so the schema does the heavy lifting. The description adds nothing about the identifier beyond reinforcing 'one credit union', which is the baseline-3 case.

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?

The description states a concrete retrieval action and resource: 'Latest snapshot for one credit union', with the source (NCUA) named. The singular 'one credit union' implicitly distinguishes it from the plural listing tool 'credit_unions', but it never explicitly names or contrasts any sibling, so it stops short of a 5.

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 only implied: 'one credit union' signals a single-entity detail lookup versus a list, and 'Latest snapshot' signals current-period data. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to alternatives such as credit_union_trends for historical series or cu_peer_benchmarks for comparison.

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