Cubi Estate

Get contact options

get_contact_options

Read-only

How a buyer can reach the agent for one Cubi Estate listing.

Read-only: lists the available contact methods (send the agent questions
via Cubi, message Cubi on WhatsApp/Telegram, send a request by email),
suggested questions the listing does not already answer, and the links
that start each one. Nothing is sent to anyone, and the agent's phone
number or email is never returned — Cubi runs agent contact through its
own consented flow.

Args:
    listing_id: The listing URL exactly as shown in a search result, or a
        source-prefixed id from a prior result (e.g. `remax:12345`).
    lang: ISO 639-1 language code for the suggested questions. Defaults to en.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_contact_options"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	ISO 639-1 language code for the suggested questions. Defaults to en.	en
`listing_id`	Yes	The listing URL exactly as shown in a search result, or a source-prefixed id from a prior result (e.g. `remax:12345`).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 11, 2026

addedInput schema / properties / lang / description

Added value: +"ISO 639-1 language code for the suggested questions. Defaults to en."

addedInput schema / properties / listing_id / description

Added value: +"The listing URL exactly as shown in a search result, or a source-prefixed id from a prior result (e.g. `remax:12345`)."

First observedOct 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already mark this read-only and non-destructive, and the description goes well beyond them: it states 'Nothing is sent to anyone', that the agent's phone number and email are never returned, and that contact runs through a consented flow. That last point is operationally important — it stops an agent from retrying to obtain raw contact details that the API deliberately withholds.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prose portion is well front-loaded, but the trailing Args block largely duplicates text already present in the input schema, which is wasted space. Omitting it would lose nothing and would let the substantive privacy note stand out more.

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?

For a two-parameter read tool with an output schema, the description covers purpose, returned categories, privacy constraints, and identifier format. Nothing an agent needs in order to invoke it correctly is missing.

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 Args section reproduces the property descriptions essentially verbatim (listing URL or source-prefixed id; ISO 639-1 language code, default en). It adds no format examples or edge cases beyond what the schema already documents, so the baseline of 3 applies.

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 opening sentence names the specific resource and scope ('How a buyer can reach the agent for one Cubi Estate listing'), then enumerates exactly what is returned: contact methods (Cubi, WhatsApp/Telegram, email), suggested questions, and start links. No sibling tool deals with contact methods, and the description makes that boundary obvious without opening any schema.

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?

Usage context is clear: the tool operates on a single listing identified by a URL from a search result or a source-prefixed id from a prior result, which implicitly tells the agent to call it after a listing lookup. There is no explicit when-not or named alternative, but no sibling overlaps enough to create real ambiguity.

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

All Cubi Estate 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?