Skip to main content
Glama

Stratalize Intelligence

Get Mortgage Market Benchmark

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new operational context: the upstream source (FRED weekly survey), the staleness contract ('Rates update weekly'), and a per-call price of $0.02 USDC, which is essential for an agent deciding whether to spend. It does not describe pagination or response shape, keeping it below 5.

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?

One front-loaded sentence carries the resource and its contents, followed by three short scoping sentences for audience, cadence, and price. The middle list is dense but each item is informative; nothing is redundant, though the comma-heavy enumeration is slightly harder to scan than a structured breakdown would be.

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 only two optional parameters and no output schema, the definition does enough to establish what data comes back, how fresh it is, and what it costs. However, it leaves the two input parameters entirely unexplained and does not state whether results are national, per-state, or broken out by loan type — a real gap for a procurement-priced, open-world data tool.

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% and the description compensates for none of it: it never mentions the 'state' filter or the 'loan_type' enum values (conventional, fha, va, jumbo). The enumerated content items are data categories returned, not inputs, so the agent gets no help understanding how the two parameters scope the result.

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 names the resource precisely and enumerates its contents (30Y/15Y fixed from FRED, ARM spreads, points and fees, DTI standards, affordability index), which implicitly separates it from get_rental_market_benchmark or get_residential_market_benchmark. It never explicitly contrasts itself with those siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only routing signal is an audience list ('For homebuyers, lenders, real estate agents, and housing analysts'), which describes who consumes the data rather than when to call this tool versus the dozens of other benchmark siblings. There is no when-not-to-use condition and no named alternative, so an agent must infer selection from the domain vocabulary alone.

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