eventin-mcp-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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_bookingsB | Get event bookings with filters Args: page: Page number (default 1) per_page: Items per page (default 10) status: Filter by payment status (e.g., 'completed', 'failed') event_id: Filter by specific event ID |
| get_booking_statsB | Get summary statistics of bookings |
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 are clearly distinct: get_bookings returns individual booking records with filters, while get_booking_stats provides summary statistics. There is no functional overlap, making selection unambiguous.
Both tool names follow a consistent pattern: 'get_' followed by a noun, using snake_case (get_bookings, get_booking_stats). This is predictable and uniform.
With only two tools, the server feels thin and below the typical well-scoped range of 3-15 tools. While both tools are relevant to bookings, the count is borderline and may be insufficient for broader event management needs.
The server only provides read and aggregate operations (list bookings, get stats). Missing are any create, update, cancel, or delete functionalities, which are essential for a complete booking management workflow. This represents significant gaps.