Small Business Funding Finder

SBA loans that fit

sba_loans

Read-onlyIdempotent

A sourced guide to SBA-backed financing for a small business, ranked for the owner's need: 7(a) small, Standard 7(a), SBA Express, 504, Microloan, the export loans (Export Express, Export Working Capital, International Trade) and the disaster loans (physical damage and EIDL). Give any of amount_needed, purposes, years_in_business and state. Each fitting program comes with why it fits, what it is for, its maximum amount, terms, SBA's published interest-rate maximums where SBA sets them, key requirements, who makes the loan, how to apply and its official sba.gov page; programs that do not fit say why. Then the next steps: SBA Lender Match and free or low-cost counseling from SBDCs, SCORE, Women's Business Centers and Veterans Business Outreach Centers, with locator links for the state when given. Facts are from sba.gov as of 2026-11-03, returned in as_of. Use it when a for-profit small business finds few grants it qualifies for. Static reference with no network access. Informational, not financial advice.

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

Input Schema

Name	Required	Description
`state`	No	Two-letter code for a U.S. state, DC, Puerto Rico, the U.S. Virgin Islands, Guam, American Samoa or the Northern Mariana Islands, for example MT.
`purposes`	No	Every use that applies: working_capital, equipment, real_estate, buy_a_business, startup, inventory, refinance_debt, export, disaster_recovery.
`amount_needed`	No	Dollars needed, for example 40000.
`years_in_business`	No	Years the business has operated. 0 if it has not opened yet.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that this is a 'Static reference with no network access', pins the data vintage ('Facts are from sba.gov as of 2026-11-03, returned in as_of'), and warns 'Informational, not financial advice.' It also details the shape of the response: per-program fit rationale, maximums, terms, rate caps, requirements, lender type, application path, official page, plus negative results ('programs that do not fit say why') and next-step counseling resources.

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?

Purpose and the input prompt are front-loaded, and the closing sentences (data vintage, static reference, not financial advice) are genuinely load-bearing. The long middle enumeration of program names and output fields is dense and slightly list-like, but every clause maps to something the agent needs to know about the return payload.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates fully by describing the returned fields per program, the treatment of non-fitting programs, the next-steps section, and the as_of provenance stamp. For a read-only static lookup tool with four optional inputs, nothing an agent needs in order to call it and interpret results is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that state drives locator links for Lender Match and counseling partners, and that the four inputs are all optional prompts rather than required filters. It does not explain how amount_needed or years_in_business interact with program eligibility thresholds, which would have pushed it higher.

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 opens with a specific verb and resource ('A sourced guide to SBA-backed financing for a small business') and enumerates the exact programs covered (7(a), Express, 504, Microloan, export and disaster loans), plus the ranking basis ('ranked for the owner's need'). It also implicitly separates itself from the grants-oriented siblings by framing itself as the fallback when 'a for-profit small business finds few grants it qualifies for.'

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 a clear triggering condition: use it when a small business qualifies for few grants, which contrasts with search_grants/get_grant. It also states the input posture ('Give any of amount_needed, purposes, years_in_business and state'), implying all parameters are optional. It stops short of naming an explicit alternative or exclusion, so it does not reach the top band.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Small Business Funding Finder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?