Fotocasa1 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Server host (not applicable) | |
| PORT | No | Server port (not applicable) | |
| API_KEY | Yes | API 密钥 (API Key for 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| property_detailsB | Get property details. Requires the property ID. |
| list_propertiesA | List Properties. Requires locationId, lat and lon which can be obtained through autocomplete endpoint. Pick the property type value to extract Homes, Premises, Garages, Offices, Box Rooms, Lands or Buildings. |
| get_suggestionsB | Get location suggestions (autocomplete) |
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 has a distinct purpose: location autocomplete, property listing, and property details. No overlap in functionality.
Names use consistent lowercase_with_underscores pattern. Two follow verb_noun (get_suggestions, list_properties) and one is noun_noun (property_details), which slightly deviates but remains clear.
3 tools is minimal but reasonable for a read-only property browsing server. Could be expanded with search or filtering but not critically thin.
Covers the basic workflow of location search, property listing, and details. However, missing operations like filtering by criteria other than location or user interaction features reduces completeness.