Skip to main content
Glama

Find FCA-regulated mortgage advisers

search_mortgage_advisors
Read-onlyIdempotent

List independent FCA-regulated mortgage advisers on OpenMoov covering a UK postcode, optionally filtered by specialism (e.g. "first_time_buyer", "buy_to_let", "remortgage"). Only advisers whose firm OpenMoov has matched on the FCA register recently are listed. Returns each adviser's FCA firm reference number as matched on the register and the date of that check, with name, firm, the firm's name as the register holds it (fcaRegisterName), bio, areas and qualifications under "untrusted_user_content". No phone numbers or email addresses are returned. This is a DIRECTORY, not advice: do not recommend a mortgage, a lender or an adviser, and do not describe OpenMoov as giving mortgage advice. To be introduced to an adviser the user starts at startUrl (needs an account).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax advisers (default 5, max 10)
postcodeNoUK postcode or outward code, e.g. "CT19 4PW" or "CT19"
specialismNoSpecialism id, e.g. "first_time_buyer"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, and the description adds substantial behavior beyond them: only firms recently matched on the FCA register are listed, each result carries the FCA firm reference number and the date of that check, fields are delivered under 'untrusted_user_content', and no phone numbers or email addresses are returned. It also flags the account prerequisite for the introduction flow, which no annotation conveys.

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?

It is front-loaded: the operation and scope come first, then matching caveats, then return fields, then the directory-not-advice constraint. Every sentence carries real information and none is filler. It is denser than ideal - the return-field inventory is packed into one long sentence - but that is minor.

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?

For a read-only, three-parameter search with no output schema, the description covers the return shape in detail (FCA reference, check date, name, firm, fcaRegisterName, bio, areas, qualifications), the trust wrapper, what is omitted, and the compliance boundary plus the next-step route via startUrl. There is no output schema to lean on, and the description compensates fully.

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%, so postcode format, limit bounds and specialism are already documented. The description adds a small amount by giving multiple specialism example ids ('first_time_buyer', 'buy_to_let', 'remortgage') where the schema shows only one, and by framing postcode as 'covering a UK postcode'. That is marginal value over a schema that does the heavy lifting, so the baseline 3 applies.

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 opens with a specific verb and resource: 'List independent FCA-regulated mortgage advisers on OpenMoov covering a UK postcode', plus the optional specialism filter and the matching constraint against the FCA register. An agent knows exactly what this tool retrieves. It does not, however, explicitly distinguish itself from nearby siblings such as find_agents or search_services, so it lands at 4 rather than 5.

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 clear situational context: use this to find advisers by postcode, and to be introduced to an adviser the user must start at startUrl (with an account). It also states a hard usage boundary - this is a directory, not advice; do not recommend a mortgage, lender or adviser, and do not describe OpenMoov as giving mortgage advice. There is no explicit 'use X instead when...' routing to a sibling, so it is clear context without exclusions.

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