Skip to main content
Glama

get_sba_loan_market_data

Read-only

Use when assessing small business lending opportunity in a market, benchmarking a bank's SBA production against competitors, evaluating CRA lending performance by geography, or identifying industries with unmet capital needs. Returns SBA 7(a) and 504 loan approval data — counts, amounts, average sizes, top lenders, and industry concentration by state and NAICS sector. Example: Illinois manufacturing sector — 847 SBA loans approved in 2023, $425K average, top 3 lenders holding 31% market share — 69% of market accessible to community bank competition. Source: SBA Public Loan Disclosure Data. $0.10 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
yearNo
stateNo
industryNoIndustry name or NAICS code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), and the description adds real value on top: the upstream source (SBA Public Loan Disclosure Data) and the per-call cost of $0.10 USDC. What it omits is coverage limits such as which years the disclosure data spans.

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?

Front-loaded with use cases, then returns, then a worked example, then source and price — a sensible ordering with no filler sentences. The example's '69% of market accessible to community bank competition' reads as a derived interpretation rather than raw output, slightly muddying what the call actually returns.

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 carries the burden of describing returns, and it does so well, plus pricing and source. The remaining gap is input-coverage detail (year availability, state format) for a tool whose schema documents almost nothing.

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?

Only 33% of parameters have schema descriptions; year and state are bare. The description never clarifies accepted year ranges or whether state expects a two-letter code, full name, or FIPS. The Illinois/manufacturing example only weakly implies state and industry formats, leaving the low-coverage gap largely unfilled.

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?

The description names a specific resource (SBA 7(a) and 504 loan approval data) and enumerates exactly what is returned: counts, amounts, average sizes, top lenders, and industry concentration by state and NAICS sector. That is enough for an agent to distinguish it from the other market-benchmark siblings in one read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives four concrete triggering scenarios (small business lending opportunity, bank SBA production benchmarking, CRA performance by geography, unmet capital needs by industry). It stops short of naming when-not-to-use conditions or an alternative tool, which keeps it at a 4 rather than a 5.

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