Find a real estate agent

Open times

open_times

Read-only

Lists the open times for a buyer consultation or a listing appointment with the chosen brokerage. Showings are not offered.

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": "open_times"
  }
}

Input Schema

Name	Required	Description
`days`	No	How many open days to list (1 to 14, default 7).
`from`	No	First day to look at, MM/DD/YYYY. Leave out for the next open days.
`kind`	Yes	buyer_consult: the person wants to buy a home. listing_appt: the person wants to sell their home.
`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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results are tied to 'the chosen brokerage' and that showings are excluded from scope, but says nothing about how availability windows are produced, defaults, or result shape.

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 short sentences, front-loaded with the core action and closed with the scope exclusion; nothing is redundant.

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 read-only, four-parameter tool with full schema coverage and no output schema, the description supplies enough to call it correctly. A brief note on what the returned open times represent (e.g., bookable slots) would close the remaining 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 100%, so days, from, kind, and brokerage_id are already documented with formats, enum meanings, and ranges. The description only reinforces that brokerage_id identifies the brokerage whose availability is being listed, adding no syntax or interpretation beyond the schema.

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?

The description gives a specific verb and resource: it lists open times for a buyer consultation or a listing appointment with a chosen brokerage. The closing line 'Showings are not offered' draws a boundary that helps separate it from appointment-related siblings, but no sibling tool is named explicitly.

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 context is clear: use it to discover availability for the two supported appointment kinds, scoped to a brokerage. The negative statement 'Showings are not offered' acts as a when-not condition, though it never names an alternative such as book_time for actually reserving a slot.

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?