Skip to main content
Glama

Realestateapi

by io.github.pipeworx-io

Realestateapi Property Search

realestateapi_property_search
Read-onlyIdempotent

Search properties by city/state/filters (off-market, absentee-owner, value range) — returns matching properties with address, owner, beds/baths, and estimated value. Example: realestateapi_property_search({ city: "Austin", state: "TX", absentee_owner: true, value_max: 400000, size: 25, _apiKey: "your-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoZIP code
cityNoCity name, e.g. "Austin"
sizeNoMax results to return (default 10, max 50)
stateNoTwo-letter state code, e.g. "TX"
_apiKeyYesRealEstateAPI key from realestateapi.com
beds_minNoMinimum bedrooms
baths_minNoMinimum bathrooms
value_maxNoMaximum estimated value (USD)
value_minNoMinimum estimated value (USD)
property_typeNoOne of SFR, MFR, CONDO, LAND, MOBILE, OTHER
absentee_ownerNoOnly properties whose owner lives elsewhere

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-realestateapi-api-key",
+    "absentee_owner": true,
+    "city": "Austin",
+    "size": 25,
+    "state": "TX",
+    "value_max": 400000
+  },
+  {
+    "_apiKey": "your-realestateapi-api-key",
+    "baths_min": 2,
+    "beds_min": 3,
+    "city": "Denver",
+    "property_type": "SFR",
+    "state": "CO",
+    "value_max": 600000,
+    "value_min": 350000
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds specific behavioral traits: it returns matching properties with specified fields and demonstrates usage with filters. It does not contradict annotations and provides useful detail about return content.

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 two sentences plus a well-formatted JSON example. It is front-loaded with the core purpose and efficiently conveys usage. Every element is necessary and no redundancy.

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?

Given 11 parameters and no output schema, the description covers the purpose, input filters, and return fields. However, it does not describe pagination, error handling, or exact response structure. With full schema coverage and annotations, it is mostly complete but leaves some ambiguity for the agent.

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 description coverage is 100%, so the schema already documents each parameter. The description adds value by showing a concrete example with multiple parameters and mentioning defaults (e.g., size default 10, max 50). This helps the agent understand parameter interplay beyond the schema.

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 starts with 'Search properties by city/state/filters' which clearly states the action and resource. It lists specific filters (off-market, absentee-owner, value range) and mentions return fields (address, owner, beds/baths, estimated value). The sibling tools include realestateapi_property_detail, so this tool's purpose is distinct as a search function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool over alternatives like realestateapi_property_detail or realestateapi_skip_trace. It gives an example but no context about prerequisites, when not to use, or comparison with siblings.

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

All Realestateapi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Multiple tools have overlapping research/lookup purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx_grounded and validate_claim both verify claims against sources, and six polymarket_* tools overlap on edge/arbitrage detection. The three realestateapi_* tools are distinct but sit awkwardly beside 31 unrelated tools.

Naming Consistency2/5

Naming conventions are mixed: snake_case prefixed tools (realestateapi_property_search), domain-prefixed tools (polymarket_edges), verb-noun tools (ask_pipeworx, compare_entities), noun phrases (entity_profile, recent_changes), and bare verbs (remember, forget, recall). There is no consistent verb_noun pattern across the set.

Tool Count2/5

34 tools is heavy, and the vast majority belong to the Pipeworx platform rather than the Realestateapi identity — only 3 of 34 tools are real-estate specific. The count is not well-scoped for the server's stated purpose.

Completeness2/5

For a real estate API the surface is severely thin: search, detail, and skip-trace only, with no market trends, tax history, rental estimates, or comparable-sales data. For the Pipeworx meta-domain the coverage is broader, but the server presents as Realestateapi, making the domain coverage a mismatch.

Resources