Skip to main content
Glama

Realestateapi

by io.github.pipeworx-io

Realestateapi Skip Trace

realestateapi_skip_trace
Read-onlyIdempotent

Skip-trace owner contact info for an address — returns the owner name plus phone numbers and emails. Regulated PII: pure passthrough, nothing is stored. Example: realestateapi_skip_trace({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesRealEstateAPI key from realestateapi.com
addressYesFull property/mailing address to trace
last_nameNoOwner last name (optional, improves match)
first_nameNoOwner first name (optional, improves match)

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",
+    "address": "123 Main St, Austin, TX 78701"
+  },
+  {
+    "_apiKey": "your-realestateapi-api-key",
+    "address": "456 Oak Ave, Denver, CO 80202",
+    "first_name": "John",
+    "last_name": "Smith"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds that it is a 'pure passthrough, nothing is stored,' which provides extra context about data handling. It also states the return includes owner name plus phone numbers and emails, which is behavioral information beyond annotations.

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 a single sentence plus a code example, both highly relevant and front-loaded. No unnecessary words; every element serves a purpose.

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?

Given the absence of an output schema, the description sufficiently explains return values (owner name, phone, emails). Parameter descriptions and annotations cover safety and behavior. The description is complete for a well-understood third-party API tool.

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?

The input schema has 100% description coverage. The description includes an example call showing usage and notes that optional parameters last_name and first_name improve match accuracy, adding meaning beyond the schema descriptions.

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 clearly states it 'skip-traces' owner contact info for an address, returning owner name, phone numbers, and emails. The verb 'skip-trace' is specific and the resource 'owner contact info for an address' is well-defined. It distinguishes from sibling tools like 'realestateapi_property_detail' and 'realestateapi_property_search'.

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?

The description implies use when needing owner contact info for a property address. It mentions the tool is a 'pure passthrough' with no storage, which is a usage caution. However, it does not explicitly list when to use or when not to use, but the context is clear given the tool's purpose.

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