Skip to main content
Glama

Stratalize Intelligence

Get Bank Regulatory Benchmark

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
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-schema context — the underlying source (FDIC call report public aggregates) and the per-call price of $0.02 USDC — but says nothing about data recency, aggregation lag, or what the response looks like.

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?

Three compact sentences: the deliverables and dimension are front-loaded, followed by the data source, audience, and cost. The metric list is dense but every item earns its place by telling the agent what it will receive.

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?

For a two-parameter, read-only lookup with no output schema, the description is close to sufficient: it names the metrics and the source. The remaining gaps are the freshening cadence of the FDIC aggregates and the behavior of the optional bank_type filter, both of which an agent would want before calling.

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 parameter meaning, and it largely does not. The phrase 'by asset size tier' gestures at asset_size_tier, but the optional bank_type parameter (commercial/savings/cooperative) is never mentioned, nor is its default or filtering behavior when omitted.

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 exact metrics returned: CET1, Tier 1 leverage, NIM, efficiency ratio, charge-off rates, and loan-to-deposit ratio. That level of specificity separates it from generic siblings like get_bank_financial_intelligence or get_aml_regulatory_benchmark, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied through the audience statement ('For bank CFOs, risk officers, and bank analysts'), which signals the appropriate consumer but not the conditions under which to pick this tool over the many sibling benchmark tools. There is no when-not guidance and no named alternative.

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