CryptoPulse Data API

realestate_lead

[$0.01 USDC per call via x402] Submit a home BUYER or RENTER lead (United States and Canada): the customer's full contact details plus location, property type, beds/baths, budget and timeframe. The lead is offered exclusively to a vetted local real-estate agent (buy) or property manager / landlord (rent), who contacts the customer directly. Incomplete submissions return 400 with the missing fields and are not charged. REFERRAL BOUNTY: the paying wallet earns $10 USDC when a partner accepts the lead (paid weekly).

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": {
      "intent": "<intent>",
      "customer_name": "<customer_name>",
      "customer_email": "<customer_email>",
      "customer_phone": "<customer_phone>",
      "city": "<city>",
      "state": "<state>",
      "budget_max": "<budget_max>",
      "timeframe": "<timeframe>",
      "notes": "<notes>",
      "customer_consent": "<customer_consent>"
    },
    "name": "realestate_lead"
  }
}

Input Schema

Name	Required	Description
`zip`	No	Preferred ZIP / postal code(s), comma-separated, if known
`beds`	No	Minimum bedrooms, e.g. 3
`city`	Yes	City the customer wants to buy or rent in
`pets`	No	Pets, if any (e.g. 1 cat)
`baths`	No	Minimum bathrooms, e.g. 2
`notes`	Yes	Anything else the agent should know (household size, parking, accessibility, schools, work location), at least 20 characters
`state`	Yes	State or province code, e.g. FL, TX, NY, ON
`intent`	Yes	buy or rent
`country`	No	US or CA (default US)
`timeframe`	Yes	When they want to move/close: asap, 1-3 months, 3-6 months, 6-12 months, just looking
`agent_name`	No	Name of the AI agent or platform submitting the request
`budget_max`	Yes	Maximum price (buy) or maximum monthly rent (rent), number in local currency
`budget_min`	No	Minimum price (buy) or monthly rent (rent), number in local currency
`must_haves`	No	Must-have features, comma-separated: garage, yard, in-unit laundry, near transit, near masjid, ground floor, ...
`preapproved`	No	buy only: has the customer been pre-approved for a mortgage? yes, no, cash
`callback_url`	No	Optional https URL; status updates are POSTed there
`lease_length`	No	rent only: desired lease length, e.g. 12 months
`move_in_date`	No	rent only: desired move-in date YYYY-MM-DD
`agent_contact`	No	Email or URL for the agent operator
`customer_name`	Yes	Customer's full name
`neighborhoods`	No	Preferred neighborhoods or areas, comma-separated
`property_type`	No	One of: house, townhouse, condo, apartment, room, duplex, multi-family, land, commercial, other
`customer_email`	Yes	Customer's email address
`customer_phone`	Yes	Customer's phone number with country code, e.g. +1 407 555 0100
`customer_consent`	Yes	Must be 'true': the customer agreed to be contacted by a licensed agent or property manager at the phone and email given
`contact_preference`	No	call, text, whatsapp or email (default call)
`preferred_language`	No	Customer's preferred language (default English)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/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 well: it discloses the $0.01 USDC x402 cost, that incomplete submissions return 400 and are NOT charged, that the lead goes exclusively to one vetted agent/manager who contacts the customer directly, and the $10 weekly bounty. Gaps remain on response shape on success, idempotency/deduplication of repeat leads, and consent enforcement beyond the schema.

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?

The price is front-loaded in brackets, then purpose, then fulfillment, then error/billing behavior, then bounty — a sensible ordering with little waste. It is dense but proportionate to a 27-parameter, 10-required tool.

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 27-parameter mutation tool with no annotations and no output schema, the description covers cost, billing failure mode, downstream handling and payout. It could go further on the success response (lead identifier, what callback_url delivers) and on duplicate-lead handling, but it is largely sufficient.

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 baseline is 3. The description adds framing about which data constitutes a complete submission (contact details, location, property type, beds/baths, budget, timeframe), which loosely maps to the required set, but adds no syntax or format detail 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?

States a specific verb and resource (submit a buyer/renter lead), the geography (US and Canada), and the two intent branches (buy vs rent) with the downstream recipient named. Nothing here overlaps confusingly with the wallet/quote/status siblings.

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 makes clear this is the submission step for a real-estate lead and explains what happens after submission, but it gives no explicit routing guidance such as using realestate_status to check an existing lead or bridge_quote to fund the wallet. Context is clear; exclusions and sibling routing are left to inference.

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

All CryptoPulse Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?