espaciarte-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKEND_BASE_URL | No | Espaciarte backend URL | http://localhost:8000 |
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_spacesA | Search published spaces (event venues, workspaces, studios…) on Espaciarte around a geographic point, with optional filters. Returns a paginated list of public space summaries: name, venue type, capacity, pricing, photos, and approximate (obfuscated) location. |
| get_space_detailsA | Fetch the full public detail of one published Espaciarte space by id: description, rules, photos, activities, weekly availability, pricing, add-ons, and host profile. |
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 2 tools
The two tools have clearly distinct purposes: one searches for spaces with filtering, while the other retrieves full details for a specific space. There is no overlap or ambiguity in their intended use.
Both tools follow a consistent verb_noun pattern (search_spaces, get_space_details). Though the verbs differ, the structure is predictable and readable.
With only 2 tools, the server feels minimal but not absurdly thin. The scope appears to be read-only space exploration, and these two tools cover the primary needs, though more operations could be expected.
For a public-facing space discovery API, the combination of search and detail retrieval covers the core use case. Missing operations like booking or creating are outside the apparent purpose, so no critical gaps are evident.