Skip to main content
Glama

get_credit_union_benchmark

Read-only

Credit union financial performance benchmarks — capital ratios, net interest margin, loan growth, and delinquency rates by asset size. Source: NCUA quarterly call report public data. For credit union CFOs preparing for NCUA exams and board reporting. $0.02 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": {
      "asset_size_tier": "<asset_size_tier>"
    },
    "name": "get_credit_union_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
charter_typeNo
asset_size_tierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely new behavior: the data provenance and refresh cadence (NCUA quarterly call report) and a per-call price of $0.02 USDC. It stops short of describing the response shape or whether results are time-series, but the cost and source disclosures are the kind of context annotations cannot carry.

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?

Three tight sentences, front-loaded with the resource and metrics, then source, then audience, then price. No filler or repetition. The audience sentence is the weakest, reading slightly like marketing copy, but it does double as usage context.

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?

With no output schema, the description must convey what comes back; it lists the metric families, which helps, but omits units, reporting period, and whether values are single-period or a series. For a paid, benchmark-oriented tool with an undocumented second parameter, it leaves real gaps.

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%, so the description must carry parameter meaning. 'By asset size' hints at asset_size_tier, but the charter_type parameter (federal vs state) is never mentioned anywhere, and the description gives no guidance on which tier or charter to select or how segmentation affects the returned figures. The enum values are self-describing but the parameters remain largely uninterpreted.

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 resource (credit union financial performance benchmarks) and enumerates the metrics returned: capital ratios, net interest margin, loan growth, delinquency rates, segmented by asset size. The source (NCUA quarterly call report) further pins it down. It does not, however, differentiate itself from the sibling get_ncua_credit_union_financials, which an agent could easily confuse it with.

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?

The line 'For credit union CFOs preparing for NCUA exams and board reporting' implies the usage context but never states when to choose this over the NCUA financials sibling or any other benchmark tool. There are no exclusions or prerequisites, so routing must be inferred.

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