cpp-espace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESPACE_API_KEY | Yes | Your personal eSpace API key, generated from your eSpace profile |
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-work-orderA | Get details of a specific work order by ID. Use include to get related Costs, Spaces, Tasks, Attachments. |
| list-work-ordersB | List work orders with optional filters by location, status, priority, assignment, service category, or date range. |
| create-work-orderA | Create a new work order. Requires description, location, service category, and priority. ALWAYS confirm with user before calling. |
| update-work-orderB | Update an existing work order. ALWAYS confirm with user before calling. |
| delete-work-orderA | Delete a work order. ALWAYS confirm with user before calling. |
| get-work-order-spacesB | Get the spaces (rooms/areas) associated with a work order. |
| get-work-order-tasksB | Get tasks for a specific work order. |
| add-work-order-taskA | Add a task to a work order. ALWAYS confirm with user before calling. |
| update-work-order-taskB | Update a task on a work order. ALWAYS confirm with user before calling. |
| get-work-order-costsB | Get costs for a specific work order. |
| get-work-order-attachmentsB | Get file attachments for a specific work order. |
| get-work-order-prioritiesA | Get all available work order priority levels. |
| get-work-order-statusesA | Get all available work order status types. |
| get-locationsB | Get all locations for the ministry/organization. |
| get-usersB | Get all users for the ministry/organization. |
| get-categoriesA | Get all event categories for the ministry/organization. |
| get-service-categoriesA | Get all service categories (used for work orders and maintenance). |
| get-editorsB | Get all event editors for the ministry/organization. |
| get-task-templatesA | Get all task templates available in the organization. |
| get-maintenanceA | Get details of a specific scheduled maintenance item. Use include for related Spaces, Tasks, Attachments, WorkOrders. |
| list-maintenanceB | List scheduled maintenance items with optional filters. |
| get-maintenance-spacesA | Get the spaces (rooms/areas) associated with a scheduled maintenance item. |
| get-maintenance-typesB | Get all available scheduled maintenance types. |
| get-frequency-typesA | Get all available maintenance frequency types (for scheduling recurrence). |
| get-eventB | Get details of a specific event. Use include for related Spaces, Resources, Services. |
| list-eventsB | List events with optional filters by location, date range, or category. |
| get-event-spacesA | Get the space tree for an event. Returns all spaces (rooms/areas) with hierarchy, capacity, and scheduling status. |
| get-event-occurrencesB | Get occurrences of a recurring event within a date range. |
| get-equipmentA | Get details of a specific piece of equipment. |
| list-equipmentB | List all equipment with optional filters. |
| get-equipment-typesA | Get all available equipment types. |
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 31 tools
Each tool is clearly named with a distinct resource and action, avoiding overlap. Sub-resources like work-order tasks, costs, attachments are explicitly separated, making it easy for an agent to select the correct tool.
All tools follow a consistent verb-noun pattern using lowercase with hyphens (e.g., get-work-order, create-work-order, list-events). There are no deviations or mixed conventions, ensuring predictability.
With 31 tools, the count is on the higher side, but the domain covers work orders, events, maintenance, and equipment, each with several sub-resources. The tools are well-scoped to the domain, though some consolidation of related getters could reduce the count.
Work orders have full CRUD plus sub-resource operations, but events, maintenance, and equipment only have read operations (get/list) with no create, update, or delete. This leaves notable gaps for managing these core entities.