SecureLend Market

compare_business_loans

Read-only

Search SecureLend's lender database for business loan offers matching the user's criteria (loan amount, purpose, industry, annual revenue, time in business). Returns available rates, terms, funding speed, and eligibility indicators from participating lenders. Results may change over time and may include offers from SecureLend’s database and authorized third-party integrations when enabled. The user selects a lender and is directed to complete their application on the lender's own platform.

Input Schema

TableJSON Schema

Name	Required	Description
`state`	No	The state where the business is located (2-letter code).
`purpose`	Yes	The reason for the loan, e.g., 'working capital'.
`industry`	No	The industry the business operates in, e.g., 'technology'.
`loanAmount`	Yes	The desired loan amount, e.g., 50000 for $50,000.
`annualRevenue`	No	The business's gross annual revenue in USD.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`offers`	Yes
`summary`	Yes
`metadata`	Yes

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (readOnly, openWorld), the description adds critical behavioral details: results may change over time, offers may come from third-party integrations, and the user is redirected to the lender's platform to complete the application. This meaningfully extends the annotations without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences long, each adding distinct value: what it does, what it returns, result variability, and the next step. It is front-loaded with the core purpose and contains no fluff, making it appropriately concise.

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?

Given the presence of an output schema and annotations, the description covers the essential context: search criteria, return contents, variability, and post-search workflow. It does not explain edge cases or error behavior, but that is not critical for this search tool. Overall, it is sufficiently complete.

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?

While the schema descriptions fully cover each parameter, the description introduces a criterion 'time in business' that is not present in the schema, and omits the 'state' parameter. This inconsistency could mislead the agent about available parameters. The description adds no new semantic value beyond the schema and actively introduces confusion.

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 uses a specific verb ('Search') and clearly identifies the resource (SecureLend's lender database) and the scope (business loan offers matching user criteria). It distinguishes this from sibling tools that compare other product types like banking or credit cards.

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?

The description clearly implies when to use this tool: when the user needs business loan offers. It provides context by listing the matching criteria and the outcome of the search. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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

All SecureLend Market tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have clear, distinct purposes, but there are a few potentially confusing pairs. Compare_personal_banking and compare_savings_accounts overlap somewhat, and calculate_loan_payment could be mistaken for covering mortgages despite calculate_mortgage_payment existing. Overall, descriptions help resolve most ambiguity.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern throughout: compare_* for comparisons, calculate_* for calculations, display_* for forms, submit_* for submissions, and get_* for offers. All names use lowercase with underscores, creating a predictable and uniform naming scheme.

Tool Count4/5

With 22 tools, the count is on the higher side but appropriate given the broad financial marketplace domain. Each tool covers a specific product category or workflow step, so the size feels justified rather than bloated. It is slightly heavy but not excessive for the scope.

Completeness4/5

The tool surface covers comparison, calculation, lead generation, prequalification, document upload, and status tracking, forming a comprehensive marketplace workflow. Minor gaps exist, such as no tools for updating or canceling applications, but these are workarounds and the core user journey is well supported.

Resources

Need Help?