Skip to main content
Glama

Bank Screener

screener
Read-onlyIdempotent

Every FDIC-insured bank with key ratios; filter, sort, paginate. (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": "screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort field.
tierNoAsset-size tier, exactly one of: '1: >= $250B', '2: $100B-250B', '3: $10B-100B', '4: $1B-10B', '5: $100M-1B', '6: < $100M'.
limitNoMax rows to return.
stateNoTwo-letter state filter.
offsetNoPagination offset.
charterNolending (default: commercial banks, savings institutions, de novo banks), all, or one charter type such as 'Trust company'.
min_assetsNoMinimum total assets ($000s).
well_capitalized_onlyNo1 to keep only well-capitalized banks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 profile is covered. The description adds genuinely useful behavior beyond that: the data source (FFIEC + FDIC) and the unit conventions ($000s for dollar amounts, percentages for ratios). It still omits the return shape ('key ratios' is not enumerated), any pagination default when limit/offset are absent, and any caps beyond the schema's maximum.

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, each carrying distinct information: the first states scope and operations, the second states source and units. Nothing is redundant or padded, and the core capability is front-loaded.

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?

With 8 optional parameters, rich annotations, and no output schema, the definition is adequate but not complete. The biggest remaining gap is the return contract: 'key ratios' is never expanded, so an agent cannot know which fields it may sort by or what columns come back, and no default limit or total-count behavior is described.

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%, so every parameter is already documented, setting the baseline at 3. The description's unit note is the one piece of added meaning: it tells the agent that min_assets is expressed in thousands, which the bare schema does not. Beyond that it does not explain sortable field values or how tier boundaries interact with min_assets.

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 and operation set: 'Every FDIC-insured bank with key ratios; filter, sort, paginate.' That is a clear verb-plus-resource statement an agent can act on. It does not, however, distinguish this tool from closely named siblings such as 'banks', 'bank', or 'ma_screener', so the agent must infer the boundary itself.

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?

The mention of 'filter, sort, paginate' implies the intended workflow, but there is no explicit when-to-use guidance, no statement of when NOT to use it, and no named alternative for cases such as targeted deal screening or single-bank lookup. Usage is inferable but not directed.

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