Skip to main content
Glama

get_ncua_credit_union_financials

Read-only

Use when evaluating a credit union for partnership, acquisition, membership, or competitive benchmarking in a local market. Returns NCUA call report financials — assets, deposits, loans, net worth ratio, delinquency rate, and ROA — with peer comparison signals. The same financial data NCUA examiners review during examination preparation. Well-capitalized threshold is 7% net worth ratio — institutions below this face mandatory corrective action. Example: ABC Federal Credit Union — $2.1B assets, 11.2% net worth ratio (59% above minimum), 0.38% delinquency vs 0.71% peer average — financially strong, low credit quality risk. Source: NCUA Call Report Data. $0.10 USDC per call.

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": {
      "credit_union_name": "<credit_union_name>"
    },
    "name": "get_ncua_credit_union_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
credit_union_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly/openWorld/non-destructive, so the description's job is added context — and it delivers the data source (NCUA Call Report Data), per-call cost ($0.10 USDC), and interpretive framing (7% net worth threshold, delinquency vs peer average). It omits any latency, coverage/lag, or failure behavior, but the substantive additions are real value beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The when-to-use clause is correctly front-loaded, but the definition drifts into promotional material: the examiner-review comparison and the fully worked 'ABC Federal Credit Union' example consume substantial space without adding invocation guidance. The 7% threshold note earns its place; the sample institution does not.

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 two-parameter read lookup with no output schema, the description covers what is returned, where it comes from, how to interpret the key ratio, and what it costs — enough for correct invocation. The remaining hole is input formatting, which is the one thing an agent actually needs before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must carry the burden and largely does not. It never explains whether credit_union_name needs an exact legal name or a substring, nor what the optional 'state' parameter does beyond the vague 'in a local market' hint.

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 verb and resource ('Returns NCUA call report financials') and enumerates the exact fields returned (assets, deposits, loans, net worth ratio, delinquency, ROA). It is clearly a credit-union financials lookup, but it never distinguishes itself from the sibling get_credit_union_benchmark, which the phrase 'with peer comparison signals' actively overlaps with.

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?

Opens with an explicit trigger: 'Use when evaluating a credit union for partnership, acquisition, membership, or competitive benchmarking in a local market.' That is a real when-to-use statement. It gives no when-not conditions and does not name an alternative tool for the benchmark-style use case, so it stops short of full routing guidance.

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