listing

beycome_comps

Discovery stage — sold comparable listings near a location (GET /comps).

No account or prop_id needed. Supports price / beds / baths / area / lot / type filters. Use during discovery to support pricing alongside beycome_estimate.

Slow endpoint: a cold query can take up to ~1 minute to respond — this is normal, you can always retry the call if it times out. Photo URL and listing-link fields are stripped from the records to keep the response small.

Input Schema

TableJSON Schema

Name	Required	Description
`pages`	No	Number of result pages to fetch.
`beds_max`	No	Maximum beds.
`beds_min`	No	Minimum beds.
`location`	Yes	Location string (city, state, ZIP, etc.).
`baths_max`	No	Maximum baths.
`baths_min`	No	Minimum baths.
`price_max`	No	Maximum price.
`price_min`	No	Minimum price.
`lot_size_max`	No	Maximum lot size sqft.
`lot_size_min`	No	Minimum lot size sqft.
`property_type`	No	Comma-separated types (singlefamily, condo, townhouse, multifamily, manufactured, land, apartment).
`living_area_max`	No	Maximum living area sqft.
`living_area_min`	No	Minimum living area sqft.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses slow performance and retry guidance, as well as stripped fields. Does not mention destructive behavior, but it's a GET endpoint, so okay.

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?

Description is mostly concise, front-loaded with purpose, and provides necessary details. Some minor redundancy (e.g., 'during discovery' twice) but overall efficient.

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?

Given 13 parameters, 1 required, and presence of output schema, the description covers purpose, usage context, performance, data omissions, and references sibling tool. No major gaps.

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% with detailed descriptions. Description adds a summary of filter categories but no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Description clearly states 'Discovery stage — sold comparable listings near a location (GET /comps)' and distinguishes from sibling 'beycome_estimate' by saying 'Use during discovery to support pricing alongside beycome_estimate'.

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?

Explicitly says 'Use during discovery to support pricing alongside beycome_estimate' and notes that no account or prop_id is needed. Also mentions retry behavior for slow endpoint. Does not explicitly exclude other use cases or alternatives, but context is clear.

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?