Skip to main content
Glama

Bank SBA Lending

bank_sba_lending
Read-onlyIdempotent

One bank's SBA 7(a) lending by federal fiscal year: loans, dollars, average size, charge-off share. (Source: SBA 7(a) and 504 loan data.)

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": {
      "rssd_id": "<rssd_id>"
    },
    "name": "bank_sba_lending"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond them by disclosing the upstream source (SBA 7(a) and 504 loan data), the reporting granularity (federal fiscal year), and the specific metrics and a derived ratio (charge-off share) that come back.

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 sentences: the first front-loads scope, granularity, and returned metrics; the second is a compact provenance note. No filler and nothing structurally misplaced.

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?

With no output schema, the description correctly takes on the burden of naming the returned fields, which it does. The minor gap is that it never says whether all fiscal years are returned together (there is no year parameter) or how many periods come back, which an agent would want to know.

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?

There is a single required parameter with 100% schema description coverage ('Federal Reserve RSSD id'), so the schema already carries the meaning. The description's 'one bank's' only reinforces that the id scopes to a single institution; it adds no format, lookup, or validation detail beyond the schema baseline.

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 — one bank's SBA 7(a) lending — and enumerates the measures returned (loans, dollars, average size, charge-off share) at fiscal-year granularity. 'One bank's' implicitly distinguishes it from the sibling sba_lenders, which is a lender list, though that contrast is not stated outright.

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 phrase 'one bank's' suggests a single-institution lookup, and the required rssd_id reinforces that, but there is no explicit when-to-use guidance, no exclusions, and no named alternative such as sba_lenders for aggregate lender views.

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