Skip to main content
Glama

FreeRateUpdate Mortgage & Home Equity Shopping

Median home value from our shoppers

get_home_values
Read-onlyIdempotent

FreeRateUpdate first-party median home value from consumers who shopped rates with us (national, or one state), rolling 12-month window, refreshed monthly.

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

Input Schema

NameRequiredDescriptionDefault
stateNoOptional 2-letter state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the data is first-party consumer-shopper data, aggregated over a rolling 12-month window, and refreshed monthly — data freshness and provenance an agent cannot 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?

A single dense sentence that front-loads the source and metric before the scope and refresh cadence. It is slightly run-on but every clause (provenance, geography, window, refresh rate) carries information.

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-optional-parameter read tool with no output schema and rich annotations, the description covers provenance, geography, aggregation window and freshness. It stops short of saying what the response looks like (a single numeric value), but that is a minor omission at this complexity.

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% and the single optional 'state' parameter is already documented with its 2-letter pattern. The description adds only the interpretive detail that omitting state yields the national figure, which is useful but minimal at one parameter.

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 gives a specific resource and metric (median home value) plus its provenance (first-party, from consumers who shopped rates) and scope (national or one state). An agent can tell this is a home-value statistic rather than a rate or lender tool, though no sibling is named to sharpen the distinction.

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 by the parenthetical 'national, or one state', which tells the agent how to pick the scope, and the 'rolling 12-month window' sets the time frame. There is no explicit when-to-use guidance or exclusion relative to the rate/lender siblings, so the agent must infer selection.

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