Find a real estate agent

Request a consultation

request_consultation

Sends the chosen brokerage a request for a buyer consultation or a listing appointment. An agent reaches out to set a time; nothing is booked.

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": {
      "brokerage_id": "<brokerage_id>",
      "kind": "<kind>",
      "name": "<name>"
    },
    "name": "request_consultation"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	buyer_consult: the person wants to buy a home. listing_appt: the person wants to sell their home.
`name`	Yes
`about`	No	What they want, in their words.
`email`	No
`phone`	No	Give a phone or an email.
`times`	No	Days and times they prefer, in their words.
`language`	No	The language the person wants.
`assistant`	No	Which assistant is sending this.
`brokerage_id`	Yes	A brokerage id, as listed by the brokerage search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations mark this as a non-read-only but non-destructive write. The description adds genuinely useful behavioral context beyond that: the request goes to the brokerage, follow-up is human and asynchronous, and no time slot is reserved. Auth requirements and confirmation/response behavior are not covered.

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?

Two sentences, front-loaded with the action and immediately followed by the outcome constraint. Nothing is wasted.

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 request tool with no output schema, the description covers the essential expectation (a request, not a booking, with human follow-up). It leaves the return value and what happens to the submitted contact details unstated, which is a modest gap.

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 78%, so the schema already documents kind, about, times, language, assistant, and brokerage_id well. The description only loosely restates the kind enum ('buyer consultation or a listing appointment') and adds no new constraints or formats.

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?

States a concrete verb and resource: sends a consultation request to a brokerage for either a buyer consult or a listing appointment. The closing clause ('nothing is booked') distinguishes it from the booking sibling, though the sibling is not named outright.

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 'an agent reaches out to set a time; nothing is booked' clause tells the agent this is for a callback request rather than a confirmed appointment, which implicitly routes confirmed scheduling to book_time. No explicit when-not or prerequisites are given.

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

All Find a real estate agent 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?