Skip to main content
Glama
chrischall

homes-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Bulk-fetch homes.com properties (structured records only)

homes_bulk_get
Read-onlyIdempotent

Fetch up to 200 homes.com property records in one call by passing an array of URLs, with per-row errors and pending rows you can retry.

Instructions

Fetch up to 200 homes.com properties in one call and return their structured records. Pass urls: string[]. Results are ordered to match the input array and per-row errors are captured (one bad URL won't fail the whole call). Each row carries a status: ok, pending, or — on failure — the error kind (timeout / bridge_down / protocol / other, also in error_kind) with a retryable flag; the envelope reports count / ok / errored (+ pending when non-zero). Mirrors homes_get_property per-row, including extracted_features, hoa_fee, highlights, schools, lot_size_sqft + the derived lot_size_acres (null — never 0 — for condos / no-lot listings), and all standard listing fields. The raw description is omitted by default; opt back in via include_description: true. listing_agent omits the agent's telephone/email unless include_agent_contact: true. The whole call is bounded by an overall hard deadline: a single slow/hung URL never wedges the server — when the deadline is reached any unsettled row is returned with status: "pending" and a pending count so you can re-run just those URLs. Use this instead of looping homes_compare_properties (which caps at 8 + emits a redundant summary table) when you just want the records. Read-only; safe to call repeatedly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesArray of homes.com property URLs or paths (e.g. from a homes_search_properties result). 1–200 per call.
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns Homes.com's payload untouched. No field projection: this server has no verified record of which Homes.com fields matter, and inventing one would risk dropping a field a caller needs.
include_descriptionNoWhen true, include the raw listing `description` marketing prose per-row. Default false.
include_agent_contactNoWhen true, include the listing agent's `telephone` and `email` on `listing_agent`. Default false — name, job title, profile url and brokerage are returned without the contact details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.5
    • addedInput schema / properties / include_agent_contact
      Added value: +{
+  "default": false,
+  "description": "When true, include the listing agent's `telephone` and `email` on `listing_agent`. Default false — name, job title, profile url and brokerage are returned without the contact details.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv1.4.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Homes.com's payload untouched. No field projection: this server has no verified record of which Homes.com fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. First observedv1.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint), and the description adds substantial context beyond them: per-row `status` values (`ok`/`pending`/error kinds), the `retryable` flag, envelope counters, the hard deadline that prevents a hung URL from wedging the server, and default field omissions (`description`, agent contact). This is exactly the behavioral detail an agent needs to handle partial failure.

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?

Front-loaded with the core action and scope in the first sentence, then the error model, field parity, and opt-in flags. It is long and dense, but for a tool with this many distinct behaviors almost every clause carries information; only minor tightening is possible.

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?

No output schema exists, so the description carries the return contract itself: row shape, status/pending semantics, envelope counts, deadline behavior, and which fields are omitted by default. Nothing an agent needs in order to call this correctly or interpret partial results 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?

Schema coverage is 100% and the schema already documents `urls`, `view`, `include_description` and `include_agent_contact` including defaults and the enum. The description largely restates these; the only added meaning is the input/output ordering guarantee, which is really behavioral rather than parameter syntax. Baseline 3 is 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?

States a specific verb (bulk-fetch) and resource (homes.com properties), plus the scope (up to 200 per call, structured records). It also names the sibling it replaces (looping `homes_compare_properties`) and the sibling it mirrors (`homes_get_property`), so an agent can route 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 Guidelines5/5

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

Gives an explicit alternative and the condition that selects it: use this instead of looping `homes_compare_properties` (caps at 8, emits a redundant summary table) when you just want the records. Also states it is read-only and safe to repeat, and explains the re-run path for `pending` rows.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools