Skip to main content
Glama

BankRegReports

Loan-Concentration Screener

loan_concentration
Read-only

Screen banks by loan-portfolio concentration. (Source: BankRegReports.)

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": "loan_concentration"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order: cre_concentration (default), cre_loans, construction, total_assets.
stateNoTwo-letter state filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only a provenance note ("Source: BankRegReports.") and says nothing about what the screen returns, whether results are ranked, how many banks come back, or any limits — leaving the behavioral burden almost entirely on the annotations.

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 short sentences, purpose front-loaded, no wasted words. It is efficient but so terse that brevity shades into under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has optional sort/state filters and no output schema, so the description should explain what a "concentration" screen yields (a ranked list? which metric?) and how sorting interacts with the default. None of that is present, leaving the agent unsure what to expect from the call.

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%, and both parameters (sort, state) are fully documented with examples and allowed sort values in the schema. The description adds no meaning beyond that, 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?

"Screen banks by loan-portfolio concentration" gives a specific verb (screen) and resource (banks by loan-portfolio concentration), which is clearer than the bare name. It does not, however, distinguish itself from plausible siblings like screener, loan_portfolio, or bank_peer_ranking, so an agent cannot tell from the text alone which of these to pick.

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 when-to-use guidance, no stated conditions or exclusions, and no named alternative. The word "screen" only implies a filtering/ranking use case; nothing tells the agent when this beats loan_portfolio or the generic screener.

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