Realty In Au MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
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 |
|---|---|
| agentsget_listingsC | Get listings of an agent |
| agencyget_listingsC | Get listings of an agency |
| agentsdetailC | Get agent detailed information |
| agencydetailC | Get agency detailed information |
| agentslistC | List agents with options and filters |
| agencylistC | List agency with options and filters |
| auto_completeC | Get suggestions by term or phrase. The returned data will be used with .../properties/list endpoint |
| schoolslistC | List schools around a GEO location |
| propertieslookup_deprecatedB | Look for off-market property by id * Use .../properties/v2/lookup endpoint instead for more data returned. |
| propertiesv3lookupC | Look for off-market property by id |
| propertiesdetailC | Get detailed information of a property |
| propertieslistC | List properties with options and filters |
| propertiesv2lookup_deprecatedC | Look for off-market property by id |
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 13 tools
The tools have clear domains (agencies, agents, properties, schools) with distinct actions like detail, list, and get_listings, reducing major confusion. However, the three lookup tools (propertieslookup_deprecated, propertiesv2lookup_deprecated, propertiesv3lookup) overlap significantly in purpose, as they all search for off-market properties by ID, which could cause misselection despite versioning differences noted in descriptions.
Most tools follow a consistent noun_verb or noun_action pattern (e.g., agencydetail, agentslist, propertieslist), making them predictable and readable. The main deviation is auto_complete, which uses a different style, and the lookup tools have inconsistent versioning suffixes (v2, v3, _deprecated), but overall the naming is largely uniform and functional.
With 13 tools, the count is well-scoped for a realty server covering agencies, agents, properties, and schools. Each tool appears to serve a specific purpose within this domain, such as listing, detailing, and searching, without feeling overly sparse or bloated, aligning well with typical server scopes of 3-15 tools.
The tool set provides good coverage for core realty operations, including CRUD-like actions for agencies, agents, properties, and schools (e.g., list and detail functions). Minor gaps exist, such as no explicit update or delete tools, but agents can likely work around this given the server's focus on data retrieval and search, as suggested by tools like auto_complete and lookup functions.