Skip to main content
Glama

get_cra_performance_ratings

Read-only

Use when evaluating a bank's Community Reinvestment Act track record before a merger application, charter acquisition, branch expansion approval, or community lending partnership. CRA ratings — Outstanding, Satisfactory, Needs to Improve, Substantial Noncompliance — are a primary federal approval factor for bank mergers and acquisitions. A 'Needs to Improve' rating can delay or block merger approval by 12-24 months. Example: Heartland Community Bank — Outstanding CRA rating, 2023 FDIC exam, fourth consecutive Outstanding — maximum approval runway for pending acquisition of Gateway Savings Bank. Source: FFIEC CRA Ratings Database — the official federal record. $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": {
      "institution_name": "<institution_name>"
    },
    "name": "get_cra_performance_ratings"
  }
}

Input Schema

NameRequiredDescriptionDefault
institution_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnly=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the authoritative source (FFIEC CRA Ratings Database) and a per-call price of $0.10 USDC, which matters for cost-aware agents. It says nothing about return shape, matching behavior, or what happens on no-match, which limits the value added.

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 lead sentence front-loads the use case well and the cost and source notes earn their place. However, the worked example about a fictional bank's fourth consecutive Outstanding rating is promotional filler that adds no operational information, and the '12-24 months' delay claim pads the middle.

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 single-parameter lookup with no output schema, the description should tell the agent what identifying input to provide and roughly what comes back. It covers purpose, source, rating scale, and price, but omits the input format and any notion of the response payload, so it is adequate rather than complete.

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 coverage is 0% for the single parameter institution_name, so the description carries the full burden of explaining it. The only hint is an incidental example name ('Heartland Community Bank'), with no statement of whether exact legal name, ticker, or FDIC certificate number is expected, nor how ambiguous matches are resolved. This is a real gap for the one input an agent must supply.

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 makes clear this retrieves a bank's CRA performance rating and enumerates the four rating values (Outstanding, Satisfactory, Needs to Improve, Substantial Noncompliance). It does not explicitly contrast itself with the many other bank-regulatory siblings, so an agent must infer the boundary, but the verb+resource is unambiguous.

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?

It names concrete triggering scenarios — merger application, charter acquisition, branch expansion approval, community lending partnership — which is stronger than most definitions. It offers no explicit exclusions or alternative tools for adjacent bank data (e.g., financial intelligence or counterparty diligence), leaving that to the agent.

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