Skip to main content
Glama

screen_banks

Paid ($0.02 USDC on Base via x402). Rank all US banks by a metric.

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": {
      "metric": "<metric>"
    },
    "name": "screen_banks"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
orderNo
stateNo
metricYes
min_assets_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add genuinely useful, non-schema context: the call is paid ($0.02 USDC on Base via x402), which an agent must know before invoking. However, it says nothing about what happens if payment fails, whether there are rate limits, whether results are truncated, or what the response contains.

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 with zero padding, and the cost/payment caveat is front-loaded before the purpose. It is efficient, though the brevity comes at the cost of the parameter detail noted above rather than from ruthless editing of an otherwise complete statement.

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?

For a tool with five parameters, no annotations, no output schema, and zero schema coverage, the description leaves too much unspecified. An agent cannot learn the filtering options, the meaning of the metric enums, the default ordering, or the shape of the returned ranking without reading the raw schema and guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must compensate and largely does not. It mentions only 'metric' and 'all US banks,' while state, min_assets_usd, top, and order go entirely unexplained in prose, and the enum values (e.g. cre_concentration, htm_adjusted_tangible_equity_ratio) are never defined. Worse, 'all US banks' arguably misleads, since state and min_assets_usd filters exist.

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 verb and resource: 'Rank all US banks by a metric.' An agent can tell this is a ranking/scanning tool rather than a lookup, and the phrase 'all US banks' implies a bulk screen versus the single-entity siblings like get_bank_metrics. It stops short of naming a sibling or drawing the boundary explicitly, so it lands at 4 rather than 5.

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?

Usage is only implied by the word 'Rank' and the word 'all'; there is no statement of when to choose this over search_banks or get_bank_metrics, no note that filtering is available, and no warning about what happens when the payment is missing. An agent can infer the use case from the name plus verb, but nothing is explicit.

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