Skip to main content
Glama

FreeRateUpdate Mortgage & Home Equity Shopping

Get the link to the rate request form

get_start_link
Read-onlyIdempotent

The link to FreeRateUpdate's short request form for one product. This tool only returns the link and how to use it; it submits nothing. Opening the link and filling in the form with the person's own details, or giving them the link, is how a person asks lenders and brokers in our network to contact them with their own rates and options.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>"
    },
    "name": "get_start_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesWhat the person wants

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / product / enum
      Previous value: -[
      -  "heloc",
      -  "home-equity-loan",
      -  "cash-out",
      -  "refinance",
      -  "purchase",
      -  "home-improvement"
      -]New value: +[
      +  "heloc",
      +  "home-equity-loan",
      +  "cash-out",
      +  "refinance",
      +  "purchase",
      +  "home-improvement",
      +  "reverse"
      +]
  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, but the description adds a genuinely useful boundary: 'This tool only returns the link and how to use it; it submits nothing.' That preempts a wrong assumption that calling the tool requests rates on the user's behalf, and it hints the response includes usage instructions, which matters since no output schema exists.

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?

Front-loaded: the first sentence states exactly what is returned, the second forecloses the side-effect misconception, the third explains the workflow. Only mild redundancy in re-describing 'the person' and 'their own' twice.

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?

For a one-parameter lookup with no output schema, the description covers what is returned and how it is used, which is enough to call it correctly. A brief note on link lifetime or whether the link is user-specific would round it out.

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% with a single required enum parameter ('product' with seven enumerated values), so the schema already carries the meaning. The description's 'for one product' restates rather than extends it — there is no guidance on how to pick the right product value.

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 names a specific resource (the link to FreeRateUpdate's short request form) and scopes it to one product, so an agent can distinguish it immediately from siblings like get_heloc_rates or get_mortgage_rates that return rate data rather than a form URL.

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 clearly explains the intended use — opening the link and filling in the person's own details, or handing the link to the person — which tells the agent this is a referral/handoff tool. It stops short of naming alternatives or stating when not to use it (e.g., when the user only wants rate numbers, use get_heloc_rates).

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