Skip to main content
Glama

Stratalize Intelligence

Get Sba Loan Market Data

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.1/5.0
Behavior4/5

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

Annotations already establish this as a safe read-only, open-world call, and the description adds genuinely non-redundant context: the underlying source (SBA Public Loan Disclosure Data) and a per-call cost of $0.10 USDC, which matters for an agent's budget decisions. It stops short of disclosing coverage boundaries — such as the earliest available year, whether all states are present, or whether non-approved applications appear — leaving some behavioral risk undisclosed.

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?

The structure is well front-loaded: use cases first, then returned payload, then a worked example, then provenance and price. The illustrative example is longer and more narrative than a tool description needs (including a market-share interpretation), but it does concretely signal the output shape, so it mostly earns its space.

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 return values, and it does so explicitly by listing the metric families and their geographic/industry breakouts. Combined with source attribution and pricing, an agent has enough to decide and call correctly; only input-format details and data coverage limits are left unresolved.

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 coverage is only 33%: year and state carry no schema descriptions at all, and only industry is annotated. The description partially compensates by tying results to state and NAICS sector and by grounding an example in 2023 and an Illinois manufacturing filter, which implies the meaning of the free-text industry input. It still adds nothing about valid year ranges, state name versus abbreviation format, or how the two filters interact — real gaps for a 3-parameter tool with thin schema documentation.

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 and scope — SBA 7(a) and 504 loan approval data broken out by state and NAICS sector — and enumerates the returned metrics (counts, amounts, average sizes, top lenders, industry concentration). An agent can distinguish this from the mortgage, rental, and general market-intelligence siblings purely from the description.

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 opens with explicit when-to-use framing across four concrete scenarios: market opportunity assessment, competitor benchmarking of bank SBA production, CRA geography evaluation, and unmet capital needs by industry. What it lacks is any exclusion or disambiguation — it does not say when a sibling benchmark tool would be a better fit, so the routing decision still relies on the agent's own judgment.

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