Skip to main content
Glama

Houski Property Data

predict_endpoint

Predict property values over time. Billed per predicted value, which is one field on one date for one property. Required: property_id, start_date, fields. Find the property_id first with search_endpoint or properties_endpoint. Supports batch requests and parameter overrides for scenario testing.

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": {
      "api_key": "<api_key>",
      "property_id": "<property_id>",
      "fields": "<fields>",
      "start_date": "<start_date>"
    },
    "name": "predict_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
lastNoPeriods before start_date to include. A range reaching before 2021-01-01 is refused
nextNoPeriods after start_date to include. A range reaching past today is refused, because the models do not forecast
fieldsYesFields to predict: "estimate_sale_price", "estimate_list_price", "estimate_rent_monthly"
periodNoTime granularity: "day", "week", "month" (default), "year"
api_keyYesAPI key for authentication
overridesNoWhat-if changes to the property before predicting, for scenario testing. Anything left out keeps the property's real value.
start_dateYesReference date in YYYY-MM-DD format, from 2021-01-01 to today
price_quoteNoReturn the cost of this request without billing it or returning data
property_idYesProperty ID(s), comma-separated for batch requests

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?

With no annotations, the description carries the full burden and does disclose the cost model (billed per predicted value), which is a genuinely useful behavioral trait. It leaves out return shape, whether results are cached, and failure behavior for a fairly complex prediction call, so the disclosure is partial rather than thorough.

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?

Four short sentences, front-loaded with purpose, then billing, then requirements, then capabilities. The "Required: property_id, start_date, fields" line partly restates the schema's required array, but it functions as a quick pre-flight checklist and costs little.

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 9-parameter tool with no output schema, the description covers purpose, billing, ID discovery, batch, and what-if overrides. It does not sketch the response shape, which is the main remaining gap for a tool whose output schema is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the billing sentence adds real meaning: it tells the agent that widening fields, next/last, or period multiplies cost per unit. The batch note on property_id reinforces the schema's comma-separated hint with an explicit use case.

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?

"Predict property values over time" gives a specific verb and resource, and the billing sentence clarifies the unit of prediction (one field on one date for one property). It stops short of distinguishing this from the sibling avm_endpoint, which likely predicts a single value, so an agent has no explicit contrast for choosing between them.

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 supplies a concrete prerequisite and the exact siblings to use for it: find the property_id first with search_endpoint or properties_endpoint. It also notes batch and override support, but gives no when-not guidance (e.g., when to use a point-in-time AVM instead of a time series).

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