Skip to main content
Glama

High-Risk Banks

high_risk_banks
Read-onlyIdempotent

Banks ranked by the exploratory failure-risk screening score (uncalibrated, not a probability of failure). (Source: ML model.)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's real contribution is the caveat that the score is uncalibrated, not a probability of failure, and model-derived. That is exactly the kind of context an agent needs to avoid over-interpreting results. It does not state sort direction or whether all banks or only a subset are scored.

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?

A single front-loaded sentence carries the purpose, and the parentheticals carry the two essential qualifiers (uncalibrated, model source). No filler, though the double parenthetical is slightly clunky.

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 no output schema, the description should hint at what a returned row contains beyond the ranking score. It establishes the ordering and the score's meaning but leaves the returned fields (bank name, identifiers, score value, any risk indicators) unspecified.

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?

Only one parameter exists and the schema documents it fully (max rows, default 25, range 1-100), so the baseline of 3 applies. The description adds nothing about the limit, such as whether higher limits meaningfully change the ranking's tail.

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?

States a specific resource (banks) and the exact ordering criterion (exploratory failure-risk screening score), which is meaningfully distinct from the plain 'banks' sibling. It stops short of naming a sibling or explicitly contrasting the ranking with the general bank listing.

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 or when-not-to-use guidance and no named alternative. The phrase 'exploratory failure-risk screening' hints at a use case but leaves the agent to infer whether this is the right tool versus 'banks', 'risk_overview', or 'bank_ranks'.

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