Skip to main content
Glama

Antigravity x402 & MCP Gateway

fetch_fdic_bank_health

[0.005000 USDC via x402] Queries official FDIC BankFind Suite institutions data to return active US bank total assets, total deposits, equity capital, exact Decimal equity-to-assets ratio, ROA %, ROE %, and CERT ID.

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": {
      "query": "<query>"
    },
    "name": "fetch_fdic_bank_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching FDIC institutions to return (1 to 10, default 3).
queryYesActive FDIC-insured institution name keyword (e.g., 'JPMorgan', 'Citibank', 'Silicon').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.005000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It does well on provenance and cost (official FDIC source, 0.005000 USDC x402 payment), but says nothing about what happens when no institution matches, whether results are live or cached, latency, or rate limits. Safety profile is implicitly read-only from "Queries", which is a minor plus.

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 preceded by the price tag, with zero filler. However, the return fields are packed into a dense comma list, and the payment requirement is stated twice (prefix and schema), so it is efficient rather than optimally structured.

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?

No output schema exists, and the description usefully enumerates the returned metrics, which is the main thing an agent needs before calling. Remaining gaps are the empty-result behavior and any freshness/caching caveat, which are modest for a simple three-parameter read tool.

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 the schema already documents query, limit (1-10, default 3), and the optional payment signature. The description only echoes the price and the return fields; it adds no keyword-matching semantics (e.g., fuzzy vs exact name match) beyond the schema's example keywords. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Queries official FDIC BankFind Suite institutions data") plus the exact resource scope (active US banks) and enumerates the fields returned: assets, deposits, equity capital, equity-to-assets ratio, ROA, ROE, CERT ID. No sibling in the list covers FDIC bank financials, so the tool is trivially separable from the biotech, crypto, SEC, and FDA tools.

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: the reader infers this is for looking up a named US bank's financial health metrics. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative (the sibling list contains no comparable tool anyway). The "Active FDIC-insured" qualifier hints at the applicable universe but does not give task-level guidance.

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.