Skip to main content
Glama

get_mortgage_market_benchmark

Read-only

Live mortgage rate benchmarks — 30Y and 15Y fixed from FRED weekly survey, ARM spreads, points and fees, DTI standards, and affordability index. For homebuyers, lenders, real estate agents, and housing analysts. Rates update weekly. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
stateNo
loan_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely non-structured behavior: the upstream source (FRED weekly survey), the refresh cadence, and a per-call cost of $0.02 USDC. Cost and freshness are decision-relevant facts an agent cannot get from annotations.

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?

Two tight sentences front-load the resource and its contents, with cadence and price trailing. The audience list is the weakest element — moderately useful for routing but not actionable — though it costs only a clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, listing the included metrics partially substitutes for a return description, and cadence plus cost round out the operational picture. However, for a tool with two undocumented parameters and ambiguous geographic scope, the description should state what 'state' actually does before an agent calls it.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it never mentions either parameter. The 'loan_type' enum (conventional/fha/va/jumbo) is left unmapped against the listed metrics, and 'state' is unexplained — it is unclear whether it filters the benchmark or whether state-level mortgage rates even exist for a national FRED series.

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?

Names a specific resource (live mortgage rate benchmarks) and enumerates the exact data covered: 30Y/15Y fixed from the FRED weekly survey, ARM spreads, points and fees, DTI standards, affordability index. That is enough to separate it from cost, rent, or vendor benchmark siblings. It stops short of explicitly distinguishing itself from the closest neighbor, get_residential_market_benchmark, which an agent might plausibly confuse with mortgage data.

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?

The audience sentence ('for homebuyers, lenders, real estate agents, and housing analysts') implies the usage context, and the weekly update cadence tells the agent when the data is fresh. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for national vs. state-level queries, so selection still requires inference.

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