Boma MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOMA_USER_EMAIL | Yes | The email address for the Boma user account. | |
| BOMA_USER_PASSWORD | Yes | The password for the Boma user account. |
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_reservationsB | Get all room reservations, optionally filtered by date |
| get_reservations_by_roomA | Get all reservations for a specific room, optionally filtered by date |
| get_reservations_by_userA | Get all reservations for a specific user. Defaults to the authenticated user |
| get_reservationC | Get a single reservation by its ID |
| create_reservationB | Create a new room reservation. Available rooms: Big Mike, Gran Enana, Lakatán, Dacca, Cavendish, Dominico. Time slots are in 30-minute intervals |
| update_reservationC | Update an existing reservation. You can change the room, time, or date |
| delete_reservationB | Delete a reservation. Only the owner of the reservation can delete it |
| get_user_profileA | Get a user profile by ID. Defaults to the authenticated user |
| get_user_profilesB | Get multiple user profiles by their IDs. Useful for resolving emails from reservation user_ids |
| search_userC | Search for a user by email or partial email |
| get_available_roomsB | Get the list of all available rooms/spaces that can be reserved |
| get_room_availabilityB | Get the schedule for a specific room on a given date, showing all booked time slots |
| get_day_overviewA | Get a complete overview of all rooms and their reservations for a given date. Shows every room with its booked slots |
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
Every tool has a clearly distinct purpose with no ambiguity. For example, get_reservation retrieves a single reservation by ID, get_reservations gets all reservations with optional date filtering, and get_reservations_by_room focuses on a specific room. The tools are well-differentiated by their target resources and actions.
All tool names follow a consistent verb_noun pattern with clear, descriptive verbs like create, delete, get, update, and search. The naming is uniform throughout, using snake_case consistently without any deviations or mixed conventions.
With 13 tools, the count is well-scoped for a room reservation system. Each tool earns its place by covering essential operations such as CRUD for reservations, availability checks, user management, and overviews, without being excessive or insufficient for the domain.
The tool set provides complete CRUD and lifecycle coverage for the reservation domain. It includes creation, retrieval, updating, and deletion of reservations, along with availability checks, user profiles, and search functionalities, leaving no obvious gaps or dead ends for agents to handle.