Skip to main content
Glama

ZIP market stats

get_market_stats
Read-onlyIdempotent

Get a market snapshot for a ZIP code: homes for sale (active and coming soon) with the median asking price and median price per square foot, overall and by property type; rentals with the median monthly rent; sales in the last 12 months with the median sale price where sale prices are public; and the number of off-market homes. Use this for market-level questions like 'how's the market in 90210?' or 'how many homes are for sale in 78704?'

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zip_code": "<zip_code>"
    },
    "name": "get_market_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
zip_codeYesFive-digit ZIP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context the annotations lack: that sales statistics only include 'where sale prices are public', a data-completeness caveat an agent would otherwise misread as zero sales.

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?

It is front-loaded with the core action, then the metric enumeration, then the example triggers — a sensible ordering. The middle sentence is long and dense, but with no output schema each listed metric does useful work, so little is wasted.

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 available, the description fully compensates by spelling out the returned aggregates and their breakdown dimensions (overall and by property type). For a single-parameter read-only tool with complete annotation coverage, nothing essential for correct invocation is missing.

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?

There is a single parameter with 100% schema description coverage ('Five-digit ZIP code'), so the schema already carries the parameter meaning. The description adds no format, validation, or edge-case detail (e.g., what happens for an unsupported ZIP) beyond the schema, making the baseline 3 appropriate.

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 uses a specific verb and resource ('Get a market snapshot for a ZIP code') and then enumerates exactly what the snapshot contains: active/coming-soon listings with median asking price and price per square foot, rentals with median rent, 12-month sales with median sale price, and off-market counts. The phrase 'market-level questions' implicitly separates it from the property-level siblings (get_property, search_properties), so an agent can route correctly without opening a schema.

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?

It gives concrete example questions ('how's the market in 90210?', 'how many homes are for sale in 78704?') that define the intended trigger condition clearly. It does not state when not to use it or explicitly name an alternative tool for property-level lookups, so it falls short of full when/when-not guidance.

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