listing

beycome_rental_estimate

Discovery stage — estimate a property's monthly RENT (POST /gemini-estimate).

No account or prop_id needed. Pairs with beycome_estimate, but this tool is SPECIFICALLY for rental estimates: use it ONLY for rental inquiries or for properties that have a unit number. For sale-price estimates, use beycome_estimate.

Returns rentEstimate (e.g. "$2,600"), rentEstimateRange (e.g. "$2,400 - $2,800"), and the sources the figure was grounded on (source URLs are stripped to keep the response small).

Caveat: an unrecognized address still returns success: true with a generic market-average rent — check that the source titles actually reference the property's address/city before trusting the number; if they don't, treat the result as unavailable and ask the user to verify the address.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`unit`	No	Optional unit number (for example 304).
`address`	Yes	Full property address in the form 'Street, City, ST ZIP' (e.g. '501 SW 1st St, Miami, FL 33130'). ZIP is required for reliable results.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.8/5.0

Behavior5/5

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

The description discloses important behavioral traits: no account or prop_id needed, the tool returns `rentEstimate`, `rentEstimateRange`, and `sources` with URLs stripped. It also warns that an unrecognized address returns `success: true` with a generic market-average rent, and advises checking source titles before trusting the number.

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?

The description is concise, well-structured with line breaks, and front-loads the core purpose and usage. Every sentence adds necessary information, and there is no repetition or fluff.

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?

Given the presence of an output schema, the description sufficiently explains the return values and adds the critical caveat about address recognition. However, it does not cover error conditions other than the unrecognized address case, leaving a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the schema already documents the parameters. The description adds value by reinforcing that no account or prop_id is needed and that the tool is appropriate for addresses with a unit number. However, it does not add significant new syntax details 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?

The description clearly states the tool estimates monthly rent for a property, using the verb 'estimate' and the resource 'monthly RENT'. It explicitly distinguishes itself from the sibling `beycome_estimate` by specifying it is for rental inquiries or properties with a unit number, while `beycome_estimate` is for sale-price estimates.

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

Usage Guidelines5/5

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

The description provides explicit usage guidelines: use this tool ONLY for rental inquiries or properties with a unit number, and for sale-price estimates use `beycome_estimate`. It also includes a caveat about how to handle unrecognized addresses, guiding the agent on when the result may not be trustworthy.

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

All listing tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct stage or action in the listing workflow: discovery, account, creation, questionnaire, and post-publish. There is no functional overlap—even pricing-adjacent tools like comps and estimate are clearly differentiated by their outputs.

Naming Consistency4/5

All tools share the 'beycome_' prefix and lowercase underscores, but some are verbs (submit_property_link) while others are nouns (comps, offers). This minor inconsistency does not impair readability or agent selection.

Tool Count5/5

14 tools cover the full lifecycle of a real estate listing without feeling bloated or sparse. Each tool has a clear role, making the set well-scoped for the domain.

Completeness4/5

Core CRUD and lifecycle operations are present, including discovery, sign-up, listing creation, and post-publish communication. Missing are tools for updating or deleting a live listing, but the main workflow is supported.

Resources

Need Help?