Skip to main content
Glama

Credit Union Industry Ratios

industry_cu_ratios
Read-onlyIdempotent

National credit union ratios by charter type (FICU, FCU, FISCU), quarterly from June 2023. (Source: NCUA Financial Performance Report.) Values are percentages (16.08 means 16.08%); this tool returns no dollar amounts.

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

Input Schema

NameRequiredDescriptionDefault
periodNoLatest quarter shown, YYYY-MM-DD.
charterNoFICU, FCU or FISCU.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: the authoritative source (NCUA Financial Performance Report), the temporal coverage boundary (from June 2023), the unit convention (16.08 means 16.08%) and an explicit scope exclusion (no dollar amounts) that prevents misuse of the results.

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?

Two compact sentences, front-loaded with the resource and scope, followed by provenance and the unit caveat. Every clause carries information an agent needs; nothing is redundant with the title or name.

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?

With no output schema, the description must convey the return shape, and it does so adequately via the percentages convention and the explicit 'no dollar amounts' note, plus provenance and coverage period. It is slightly thin on what happens when no period is supplied, given that both parameters are optional.

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

Parameters4/5

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

Schema coverage is 100%, setting a baseline of 3, but the description adds meaning beyond the schema: 'quarterly from June 2023' constrains which period values are valid, and the enumerated charter codes are stated inline. It still does not say whether period is an as-of date or a start bound, so it stops short of a 5.

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 names the resource precisely (national credit union ratios), the breakdown dimension (charter type: FICU, FCU, FISCU) and the cadence/start (quarterly from June 2023), so an agent knows exactly what dataset is returned. It does not name or differentiate from siblings such as credit_union_trends or cu_peer_benchmarks, which is the only thing keeping it from 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is referenced. Usage is only implied by the word 'national' versus the peer/benchmark siblings, leaving the agent to infer selection criteria on its own.

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