proptech-inquiry
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Find listings by hard criteria (city, rent or sale, price ceiling, rooms, area, features, move-in date). Use this when the inquirer states requirements. Returns summaries sorted by price, cheapest first. Do not use it to answer questions about a specific listing's details; call get_listing for that. |
| get_listingA | Return the full record of one listing, including its description text. Answer only from fields present here. If the answer is not in the record, say so and hand off with reason not_answerable_from_listing instead of guessing. |
| hand_off_to_humanA | Create a ticket for the letting or sales team. You MUST use this, and not answer yourself, for: booking viewings, any price or rent negotiation, contract or legal questions, complaints, requests about personal data, and any question the listing record does not answer. Summarise the inquiry in one or two sentences so the human does not have to reread the thread. |
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 3 tools
Each tool targets a distinct action: search by criteria, retrieve one record, or escalate to a human. The descriptions explicitly define boundaries (search_listings says do not use it for a specific listing; get_listing says answer only from the record), so misselection is unlikely.
All three names follow a clear verb_noun pattern (search_listings, get_listing, hand_off_to_human) with consistent snake_case.
Three tools is lean for the narrow inquiry-handling scope, and each earns its place, though it sits near the lower bound where coverage could feel thin for edge cases.
The read-plus-escalate lifecycle is well covered: criteria search, full record retrieval, and human handoff for bookings, negotiation, legal, and unanswerable questions. Only listing management/creation is absent, which is outside an inquiry agent's stated purpose.