Skip to main content
Glama

FundBiz Lender Index

Search UK business finance lenders

search_lenders
Read-onlyIdempotent

Search the UK specialty business finance lenders that FundBiz reviews (editorial research, not a lender panel). Filter by free-text query, product type, or eligibility flags. Returns factual terms (ticket range, typical rate, decision time, soft-search, Ltd-only) plus an editorial rating. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFree-text match on name, summary and best-for tags.
ltd_onlyNoOnly lenders that lend to limited companies only.
product_typeNoSubstring match on product type, e.g. "merchant cash advance", "term loan", "asset finance", "invoice finance".
soft_search_onlyNoOnly lenders that use a soft search at quote stage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / fca_regulated_only
      Removed value: -{
      -  "description": "Only FCA-regulated lenders.",
      -  "type": "boolean"
      -}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: the data is editorial research rather than a lender panel, and the return payload contains factual terms plus a subjective editorial rating — an important distinction for how an agent should present results.

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?

Three tight sentences, front-loaded with the resource and its scope, then filters, then return shape and safety. Every clause carries information; nothing is repeated from the schema verbatim.

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 usefully enumerates the returned fields (ticket range, typical rate, decision time, soft-search, Ltd-only, editorial rating). Minor gaps remain: no mention of result limits, ordering, or pagination, which an agent might need to plan a follow-up query.

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% and every parameter already carries a precise description including examples. The description only restates the filter axes in aggregate ('free-text query, product type, or eligibility flags'), adding grouping but no new semantics beyond the schema.

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?

States a specific verb and resource ('Search the UK specialty business finance lenders') and immediately pins down the dataset's nature: editorial research, not a lender panel. That framing prevents the most likely misconception an agent could hold about this tool.

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 makes the usage context clear — this is an editorial-research lookup filterable by query, product type, or eligibility flags — and flags it as read-only. It gives no explicit when-not-to-use guidance, but no sibling tools exist to route against.

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