RateZip Bank Deposit and Mortgage Rates

Get current US mortgage rates

get_mortgage_rates

Read-only

Current mortgage rates grouped by loan type: rates RateZip observed on lenders' own published rate pages, each with note rate, APR, representative-scenario conditions, observation timestamp, source, and staleness status. No third-party national-average benchmark is redistributed. Loan types include '30-year fixed' and 'HELOC'. Pass loan_type to filter to one; omit for all grouped by type. Compare only within the same loan type. Factual rate data only: never estimate or invite a personalized quote, imply approval, or recommend a lender. Pass max_results to cap the number of rows and include_provenance=false for a shorter response.

Input Schema

TableJSON Schema

Name	Required	Description
`state`	No	Two-letter state — adds an availability/licensing note
`loan_type`	No	Loan type to filter to, e.g. '30-year fixed', '15-year fixed', or 'HELOC'. Omit for all.
`loan_amount`	No	Loan amount in USD — flags conforming vs jumbo (does not fabricate a rate)
`max_results`	No	Cap the number of observed rows returned, in the payload's ordering. Omit for all.
`credit_score`	No	FICO — returns EDUCATIONAL context only; never a fabricated credit-adjusted rate
`include_provenance`	No	false omits the per-source provenance block (snapshot ids, attributions); each row keeps its own observed_at and source_url.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

addedInput schema / properties / include_provenance

Added value: +{
+  "description": "false omits the per-source provenance block (snapshot ids, attributions); each row keeps its own observed_at and source_url.",
+  "type": "boolean"
+}

addedInput schema / properties / max_results

Added value: +{
+  "description": "Cap the number of observed rows returned, in the payload's ordering. Omit for all.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

First observedAug 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the data provenance model (lender-published pages, staleness status, no redistributed national benchmark) and explicit conduct constraints (never estimate, no personalized quotes, no approval implications, no lender recommendations). This is meaningful behavioral context an agent could not get from structured fields.

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?

Front-loads the core output description and then the filtering/usage rules in an efficient run of sentences. Minor redundancy between the loan_type sentence and the filter instruction, but nothing is filler.

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?

With no output schema, the description carries the return-value burden and does so thoroughly: row fields, representative-scenario conditions, timestamps, source, and staleness. It also documents the provenance toggle, so an agent can call it correctly without guessing.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds relationship-level meaning: loan_type omission yields all types grouped, max_results caps rows in payload ordering, and include_provenance=false shortens the response while preserving per-row observed_at/source_url.

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 (get) and resource (mortgage rates) and defines the scope precisely: rates observed on lenders' own published pages, grouped by loan type. The named loan types ('30-year fixed', 'HELOC') and provenance fields distinguish it from the deposit/CD/savings sibling tools.

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?

Explicit about filtering behavior ('Pass loan_type to filter to one; omit for all grouped by type') and adds a real analytical constraint ('Compare only within the same loan type'). It does not, however, name sibling tools or say when to prefer them over this one.

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

All RateZip Bank Deposit and Mortgage Rates tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?