Skip to main content
Glama

SBA Lender Ranking

sba_lenders
Read-onlyIdempotent

SBA 7(a) or 504 lenders ranked by dollars approved in a federal fiscal year. (Source: SBA 7(a) and 504 loan data.)

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_lenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
fyNoFederal fiscal year.
typeNoall or Bank.
programNo7A or 504.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so the safety profile is covered. The description adds the data source and the ranking metric, but says nothing about how many lenders are returned, ordering direction, or behavior when optional filters are omitted.

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?

Two short sentences with the core purpose front-loaded; the parenthetical source note is small and earns its place as provenance. No redundant restatement of the tool name.

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

Completeness3/5

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

With all three parameters optional and no output schema, the description should say what defaults apply (which fiscal year, which program) and roughly what the ranking returns. Those gaps matter for correct invocation even though the tool is otherwise simple.

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 100%, so each of fy, type, and program is already documented in the schema. The description reinforces that fy is a federal fiscal year and program is 7(a) or 504, but adds no format, default, or validation detail beyond that 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?

States a specific verb and resource: SBA 7(a)/504 lenders ranked by dollars approved, scoped to a federal fiscal year. An agent knows exactly what the tool returns, though it does not differentiate itself from siblings like bank_sba_lending or bank_peer_ranking.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The reader must infer from the phrase 'ranked by dollars approved' that this is the ranking view rather than the raw lending view.

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