stream-estate
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STREAM_ESTATE_API_KEY | Yes | Your Stream.estate API key | |
| STREAM_ESTATE_BASE_URL | No | API base URL | https://api.stream.estate |
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 |
|---|---|
| get-citiesA | Search French cities by name, zipcode, INSEE code, or geographic polygon. Returns city IDs needed for property search filters. |
| location-autocompleteA | Autocomplete cities and departments by search query. Returns IDs needed for location filters in search-properties and create-search. |
| get-points-of-interestA | Find points of interest (schools, hospitals, restaurants, parking) near a location. Returns facilities within a radius of given coordinates. |
| get-price-per-meterB | Get price per m² statistics (average, median, time series) for properties matching filters. Useful for market analysis and property valuation. |
| search-propertiesA | Search French real estate properties with extensive filters for location, price, size, rooms, energy rating, and more. Returns paginated results with property details, adverts, photos, and nearby stations. Use location-autocomplete first to resolve city/department IDs. |
| get-propertyA | Get full details for a single property by UUID, including all adverts, price history events, photos, contact info, and nearby transit stations. |
| find-similar-propertiesA | Find properties similar to a given property. Useful for market comparisons and finding alternatives. |
| create-searchC | Create a saved search with optional webhook notifications for real-time property alerts. Configure location, price, size filters and webhook endpoints. |
| list-searchesA | List all saved searches for the authenticated user. Can filter by notification status and title. |
| get-searchA | Get details of a specific saved search by its ID. |
| update-searchA | Update an existing saved search with new criteria, filters, or webhook configuration. |
| delete-searchA | Delete a saved search by its ID. |
| test-webhookA | Test webhook delivery by sending a simulated match or event payload to an endpoint. Useful for verifying webhook integration. |
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
Most tools target distinct resources and actions. The only potential confusion is between get-cities and location-autocomplete, which both resolve location identifiers, but their descriptions clarify different use cases (exact search vs autocomplete).
The majority follow a consistent verb_noun pattern (search-properties, create-search, update-search). However, location-autocomplete deviates from this pattern by placing the noun first, which is a minor inconsistency.
13 tools is well within the appropriate range for a real estate search API, covering property discovery, saved search management, location resolution, and auxiliary features like webhooks and pricing stats. Each tool has a clear role.
The tool set provides full CRUD for saved searches, comprehensive property search and detail retrieval, location resolution, and market analysis. No significant gaps for the stated domain of French real estate search.