Realty In Ca1 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Not applicable | |
| PORT | No | Not applicable | |
| API_KEY | Yes | API 密钥 (API Key for Realty In Ca1 API authentication) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have distinct purposes targeting different resources (agents, keywords, locations, properties), but there is some overlap between 'locationsauto_complete' and 'locationsv2auto_complete' which could cause confusion about which to use. The property-related tools are well-differentiated by their specific functions.
The naming follows a general pattern of resource_action (e.g., agentslist, propertiesdetail), but there are inconsistencies like 'propertiesget_demographics' (missing underscore), 'propertiesget_statistics_deprecated' (mixed conventions), and the v2 suffix in 'locationsv2auto_complete'. This mixed approach reduces predictability.
With 12 tools, this is well-scoped for a real estate server covering agents, locations, and properties. Each tool appears to serve a specific purpose without obvious bloat, and the count supports comprehensive functionality without being overwhelming.
The toolset provides good coverage for real estate queries, including listing, details, filtering, and location-based data. Minor gaps exist, such as no explicit tools for creating or updating listings (likely read-only), but agents can work around this for typical search and analysis tasks.