Skip to main content
Glama

Recent market changes

get_recent_changes
Read-onlyIdempotent

Get recent market changes: new listings, price cuts, price increases, homes that just sold, went pending, fell through, came back on the market, or were delisted. Filter by state, ZIP, or change type. Each event carries the Straply property ID, so follow up with get_property for full details and history. Use this for questions like 'what just sold in Austin?', 'any price cuts in 90210 this week?', or 'show me new listings in Texas'.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days of changes to include (1 = the most recent day)
limitNoMax events to return (default 50)
stateNoTwo-letter state code (e.g. 'CA')
offsetNoPagination offset
zipCodeNoFive-digit ZIP code
changeTypeNoFilter to one kind of change. Omit for all market events. Comma-separate for several (e.g. 'price_cut,just_sold').
includeAllNoInclude non-market data churn (mostly reference-price movement on off-market homes). Off by default — it is ~76% of raw changes and is rarely what a question is about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds that each event carries a property ID for chaining, but it does not disclose result ordering, pagination behavior, or the default exclusion of non-market churn.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then filters, follow-up behavior, and examples. Every sentence is useful and appropriately sized.

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 read-only listing tool with full parameter descriptions and strong annotations, the definition is nearly complete. The main gap is that without an output schema, it does not describe the full shape of a change event beyond the property ID.

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 description coverage is 100%, so the schema already documents all seven parameters. The description only restates the state, ZIP, and change-type filtering at a high level, adding no syntax or constraint details beyond the schema.

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 uses a specific verb and resource, 'Get recent market changes,' and enumerates the event types returned. It explicitly positions get_property as a follow-up tool, but it does not differentiate this tool from get_change_summary or get_market_stats.

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 that establish when to use the tool and notes that get_property should be used afterward for full details. It does not state exclusions or when to prefer the summary/statistics siblings.

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