Skip to main content
Glama

Growth Leaderboard

growth
Read-onlyIdempotent

Banks ranked by YoY growth in assets, loans, or deposits. (Source: FFIEC + FDIC.) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "growth"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoasset_growth | loan_growth | deposit_growth.
tierNoAsset-tier filter.
limitNoMax rows to return.
charterNoall to include trust, card, custody and de novo charters (default: commercial banks and savings institutions only).
organicNo1 to rank organic growth only (excludes acquisitions).
min_age_yearsNoMinimum charter age in years (default 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: the data provenance (FFIEC + FDIC) and, importantly, the units of returned values ($000s and percentages). It does not mention pagination, default ordering, or row-count behavior, so it is additive but not rich.

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?

Two tight sentences with the purpose front-loaded, followed by provenance and unit conventions. No filler or repetition; the only mild redundancy is the source parenthetical, which is still informative.

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 six-parameter, all-optional read-only leaderboard with no output schema, the description covers what the tool produces, the ranking dimension, and the unit conventions an agent needs to interpret results. The main gap is that it does not clarify defaults (e.g., limit or tier behavior) or describe row contents, but the schema carries the parameter detail.

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 description coverage is 100%, so every parameter is already documented in the schema, including the sort enum-like values, tier, charter, organic, and min_age_years. The description adds only the output-unit context, not per-parameter meaning, 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 verb and resource: banks ranked by YoY growth, with the three growth dimensions matching the 'sort' parameter. It is clear what the tool returns, though it does not explicitly distinguish itself from siblings such as bank_ranks or bank_peer_ranking.

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 or when-not-to-use guidance, and no alternative tools are named. An agent must infer from the name and purpose that this is the leaderboard-style growth view rather than a time-series or peer-comparison view.

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