Skip to main content
Glama

get_bank_financial_intelligence

Read-only

Use when evaluating a bank for acquisition, partnership, correspondent banking, or competitive analysis in a local market. Returns FDIC-sourced assets, deposits, capital ratios, loan quality, and peer benchmark positioning. Example: Midwest Community Bank — $2.4B assets, CET1 12.3% (well above 6% minimum), NPL ratio 0.42% vs 0.71% peer median — strong capital position, favorable acquisition target profile. Source: FDIC BankFind synced call report data. $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": {
      "bank_name": "<bank_name>"
    },
    "name": "get_bank_financial_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
bank_nameYese.g. JPMorgan, Wells Fargo, First National Bank

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuine value beyond that: the FDIC BankFind call-report data source and a $0.02 USDC per-call price, which is the kind of cost signal an agent needs. However it says nothing about data freshness/lag, or how an ambiguous or free-text bank name is resolved when several institutions match — a real risk for a single-string lookup.

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?

Front-loaded with the 'Use when' trigger, followed by return contents, then an example, source, and price — a logical order with no filler sentences. The worked example is longer than strictly necessary, but it usefully shows the shape of the returned metrics and interpretation.

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 compensates by enumerating the returned metric families and demonstrating them in a sample result. For a one-parameter read-only tool this is nearly sufficient; the missing pieces are name-resolution behavior and whether figures are point-in-time or multi-period.

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 coverage is 100% and the single required parameter carries its own examples ('JPMorgan, Wells Fargo, First National Bank'). The description adds no guidance on name format, legal-name vs. trade-name matching, or ticker/CERT acceptance, so it does not improve on the schema; baseline 3 applies.

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 concrete verb-and-resource pair: it 'Returns FDIC-sourced assets, deposits, capital ratios, loan quality, and peer benchmark positioning' for a named bank. The 'local market' framing and the FDIC call-report sourcing differentiate it from sibling diligence/benchmark tools without naming them explicitly, so an agent can infer the split but isn't told.

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?

The opening clause gives explicit use cases: acquisition evaluation, partnership, correspondent banking, competitive analysis. It stops short of exclusions or naming an alternative such as a counterparty-diligence or regulatory-benchmark tool, so the agent must infer when a sibling is the better pick.

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