Skip to main content
Glama

get_bank_regulatory_benchmark

Read-only

Bank regulatory capital and financial performance benchmarks — CET1, Tier 1 leverage, NIM, efficiency ratio, charge-off rates, and loan-to-deposit ratio by asset size tier. Source: FDIC call report public aggregates. For bank CFOs, risk officers, and bank analysts. $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_bank_regulatory_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
bank_typeNo
asset_size_tierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world access, so the bar is lower; the description still adds real value by disclosing the data source (FDIC public aggregates) and a per-call cost of $0.02 USDC, which is critical for an agent deciding whether to invoke. It omits update cadence, reporting periods, and units, keeping it short of a 5.

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?

A single dense sentence-block that front-loads the metric inventory, then the source, audience, and price in descending order of importance. Every clause carries information; nothing is redundant boilerplate.

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 simple two-parameter read-only lookup, the description covers what is measured, where the data comes from, and what it costs. It leaves open the reporting period, units/currency of the ratios, and how the response is segmented, which matter for interpreting benchmark numbers correctly.

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 the parameter burden, but it never explains asset_size_tier (the required argument) or bank_type. The phrase 'by asset size tier' only faintly signals that results are segmented by the required tier, and it says nothing about how bank_type narrows or groups the output.

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 a specific resource (bank regulatory capital and financial performance benchmarks) and enumerates the concrete metrics covered — CET1, Tier 1 leverage, NIM, efficiency ratio, charge-off rates, loan-to-deposit ratio — plus the source (FDIC call report aggregates). It is clearly distinguishable from most siblings, though it does not explicitly separate itself from near-neighbors like get_bank_financial_intelligence or get_credit_union_benchmark.

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?

The only guidance is an audience statement ('For bank CFOs, risk officers, and bank analysts'), which tells an agent who cares but not when to call this versus alternatives. There is no mention of when not to use it, what prerequisites exist, or which sibling covers a related-but-different need.

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