Skip to main content
Glama

Bank Compare

bank_compare
Read-onlyIdempotent

Side-by-side comparison of multiple banks. (Source: FFIEC Call Report.) Dollar amounts are in thousands of US dollars ($000s); 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": {
      "rssd_ids": "<rssd_ids>"
    },
    "name": "bank_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idsYesComma-separated RSSD IDs to compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 and determinism profile is covered. The description adds genuinely useful context the annotations cannot: the data source (FFIEC Call Report) and the units of returned values ($000s and percentages). It says nothing about limits on the number of banks, response shape, or handling of invalid RSSD IDs.

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 with the core purpose front-loaded and unit conventions following immediately. Nothing is padded or redundant.

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 one-parameter read-only tool with full schema coverage and no output schema, the definition covers purpose, source, and unit conventions. The main remaining gap is what fields the comparison returns and whether there is a cap on the number of RSSD IDs, which matters for a multi-entity comparison.

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 rssd_ids parameter already documents its comma-separated format with an example. The description adds no parameter-level meaning beyond the schema, so the baseline of 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?

The description states a specific operation and resource: a side-by-side comparison across multiple banks, sourced from the FFIEC Call Report. That distinguishes it reasonably from single-bank tools like bank_profile or bank_deep_dive, though it does not name a sibling explicitly.

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 and no mention of alternatives such as bank_peer_ranking, bank_trends, or bank_deep_dive. The only implied guidance is that multiple banks are involved, leaving the agent to infer the selection criteria from sibling names alone.

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