Skip to main content
Glama

FreeRateUpdate Mortgage & Home Equity Shopping

HELOC and home equity loan rates

get_heloc_rates
Read-onlyIdempotent

Today's As Low As rates for a home equity line of credit (HELOC) and a home equity loan, the same published revision as get_mortgage_rates, with each example scenario, including the existing first-mortgage balance and the combined loan-to-value it implies. Advertised rates for a stated example, not a quote.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the bar is lower, and the description still adds real behavioral context: the figures are advertised 'As Low As' examples tied to a specific published revision, and each scenario carries the existing first-mortgage balance and resulting combined loan-to-value. That tells an agent how to interpret and pair the numbers. It stops short of specifying the rate type (note rate vs APR) or the refresh cadence.

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 that front-loads the resource and rate type, then layers provenance and the example-scenario caveat. Every clause adds information, though the sentence is long enough that the 'not a quote' caveat arrives late rather than leading.

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 zero parameters, no output schema, and full annotation coverage, the description supplies what the structured fields cannot: what the numbers represent, how the example scenario is constructed, and the caveat that they are advertised rather than quoted rates. Only the rate definition (APR vs interest rate) is left to be discovered from the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no input parameters, so the baseline is 4, and the description goes further by explaining the scenario composition (first-mortgage balance and implied CLTV) that shapes the returned rates. No schema-level parameter meaning is left unexplained.

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 the specific verb+resource ('Today's As Low As rates for a home equity line of credit (HELOC) and a home equity loan') and scopes it to the same published revision used by get_mortgage_rates, which separates it from the mortgage-rate sibling. The closing clause 'Advertised rates for a stated example, not a quote' sharpens what exactly is being retrieved.

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 implied rather than stated: an agent learns the data is an advertised example rather than a personalized quote, which is interpretation guidance rather than selection guidance. It never explicitly says when to prefer this over get_mortgage_rates or the lender-level tools, though with zero parameters and a self-describing product scope the alternatives are largely self-evident.

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