Find a real estate agent

Find brokerages for an area

find_brokerages

Read-only

The real estate brokerages that serve a place and can be booked or asked here. Not a ranking.

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": {
      "place": "<place>"
    },
    "name": "find_brokerages"
  }
}

Input Schema

Name	Required	Description	Default
`place`	Yes	A city and state, a ZIP code or an address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false. The description adds a useful behavioral caveat with 'Not a ranking,' but it does not clarify ordering, result shape, rate limits, or what 'asked here' actually means operationally.

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?

Two short sentences with no filler, and the key scope is front-loaded. The fragment 'Not a ranking' is punchy but slightly cryptic, and 'asked here' could be clearer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter discovery tool with annotations covering read-only behavior, the description is minimally adequate. It still leaves unclear what 'can be booked or asked here' means, how results relate to about_brokerage, and whether coverage is exhaustive or filtered.

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 coverage is 100%, and the place parameter already documents accepted inputs as city/state, ZIP, or address. The description merely refers to 'a place' and adds no additional format or matching semantics 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 identifies the resource concretely: real estate brokerages that serve a place and are actionable for booking or questions. The verb is implicit through the tool name, but the scope and result type are clear enough to distinguish this from a generic search or ranking.

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

Usage Guidelines3/5

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

The phrase 'can be booked or asked here' implies this is a discovery step before booking or consultation, but it does not explicitly say when to choose this over siblings like about_brokerage, check_area, book_time, or request_consultation. Usage is implied rather than stated.

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?