Skip to main content
Glama

Motel Loans: hotel loan sizer and franchise costs

SBA 7(a) and 504 terms for hotels

get_sba_hotel_loan_terms
Read-onlyIdempotent

The SBA program terms motel.loans publishes for hotel and motel loans: SBA 7(a) maximum variable and fixed rates, loan and guaranty limits, equity, DSCR and maturity rules, FY 2027 guaranty fees; SBA 504 structure, debenture limit, jobs rule, fees and the latest 25-year rate. Each with its SBA or source link and effective date.

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

Input Schema

NameRequiredDescriptionDefault
programNoWhich program. Default both.both

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful behavioral context beyond that: every figure ships with its SBA or source link and an effective date, and FY 2027 fees are explicitly dated — telling the agent the data is versioned and citable, which matters for a rate/terms lookup. It does not describe pagination or response shape, but with no output schema the enumeration of returned fields largely compensates.

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?

A single dense sentence front-loads the scope ('SBA program terms for hotel and motel loans') before listing the covered data points. Every clause carries information, though the enumeration is long enough to read as a list of features rather than a prioritized summary.

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 and only one optional parameter, the description does the heavy lifting well by enumerating what comes back (7(a) rates, limits, equity, DSCR, maturity, FY 2027 fees; 504 structure, debenture limit, jobs rule, fees, 25-year rate) plus provenance. The main remaining gap is routing guidance relative to size_hotel_loan, which the description never addresses.

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 description coverage is 100% and the single enum parameter is already fully documented with its values and default in the schema. The description adds only implicit context (that 'both' yields both program families), so it neither extends nor undermines the schema. Baseline 3 is appropriate.

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 (SBA 7(a) and 504 terms for hotels/motels) and enumerates the exact data points returned (rates, limits, equity, DSCR, maturity, guaranty fees, 504 structure). It is clear what the tool delivers, though it never states a verb like 'retrieve' or 'return' and does not differentiate itself from size_hotel_loan, which an agent might reasonably confuse it with.

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 framing as 'the terms motel.loans publishes' suggests reference lookup rather than calculation, which distinguishes it in spirit from size_hotel_loan. However, there is no explicit when-to-use statement, no mention of the sibling sizing tool, and no guidance on when to pick program=both versus a single program beyond the schema default.

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