MCP Seat Reservation Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_officesC | Get all offices |
| get_officeC | Get specific office by ID |
| get_office_seatsB | Get all seats for a specific office |
| get_reservationsC | Get reservations with optional date filtering |
| get_reservationC | Get specific reservation by ID |
| create_reservationC | Create a new seat reservation |
| update_reservationC | Update an existing reservation |
| cancel_reservationC | Cancel a reservation by ID |
| get_available_seatsC | Get available seats for a specific period |
| find_seat_by_numberC | Find a seat by seat number in an office |
| get_all_commentsB | Get all comments across all seats |
| get_seat_commentsC | Get comments for a specific seat |
| add_commentC | Add a comment to a seat |
| delete_commentC | Delete a comment by ID |
| get_comment_countsC | Get comment count for each seat |
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 15 tools
Every tool has a clearly distinct purpose targeting specific resources and actions with no ambiguity. For example, 'create_reservation' and 'update_reservation' handle different lifecycle stages, while 'get_available_seats' and 'get_office_seats' serve different query needs. The descriptions make it easy to distinguish between tools like 'get_all_comments' (global) and 'get_seat_comments' (specific).
All tools follow a consistent verb_noun pattern using snake_case throughout, such as 'create_reservation', 'get_available_seats', and 'update_reservation'. The naming is predictable and readable, with verbs like 'get', 'create', 'update', 'cancel', 'add', 'delete', and 'find' applied consistently to appropriate nouns like 'reservation', 'seat', 'comment', and 'office'.
With 15 tools, the count is well-scoped for a seat reservation domain, covering offices, seats, reservations, and comments comprehensively. Each tool earns its place by addressing specific operations without redundancy, such as separate tools for managing reservations versus comments, and it avoids being too thin or bloated for the apparent scope.
The tool set provides complete CRUD/lifecycle coverage for the seat reservation domain, including offices (get), seats (find, get, check availability), reservations (create, get, update, cancel), and comments (add, get, delete, count). There are no obvious gaps; agents can perform full workflows from browsing offices to managing reservations and comments without dead ends.