Skip to main content
Glama

Credit Union Trends

credit_union_trends
Read-onlyIdempotent

Quarterly metric time series 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_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
cu_numberYesNCUA charter number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely useful unit semantics not present in annotations or schema: dollar amounts are in thousands and ratios are percentages, including the rationale that NCUA files whole dollars and the API divides by 1,000. It stops short of describing the metrics covered, the number of periods returned, or ordering.

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 short sentences, front-loaded with the core purpose, followed by source and unit conventions. The parenthetical explanation of the $000s conversion earns its space because it prevents a real misinterpretation by the agent.

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 one required parameter, no output schema, and full annotation coverage, the definition is serviceable, but it never indicates which metrics the series contains, how many quarters are returned, or how the series is ordered. For a time-series tool those omissions leave the agent guessing about the response, even though the units are handled well.

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 the NCUA charter number with an example, so the schema carries the load. The description adds nothing about the identifier beyond that baseline, so a 3 is appropriate.

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 and shape: a quarterly metric time series scoped to a single credit union, with NCUA as the source. This differentiates it from aggregate or multi-institution tools in spirit, though it does not name a sibling such as credit_unions or credit_union directly.

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 guidance, no prerequisites, and no named alternative for retrieving aggregate or peer-level data. The phrase 'for one credit union' implies single-entity scope, but the agent must infer when to pick this over the many other trend and profile siblings.

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