TryBooking MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRYBOOKING_REGION | Yes | Region code: au (Australia), nz (New Zealand), uk (United Kingdom), or us (United States) | |
| TRYBOOKING_API_KEY | Yes | Your TryBooking API key | |
| TRYBOOKING_SECRET_KEY | Yes | Your TryBooking secret key |
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_account_transactionsA | Retrieve account transactions for a date range |
| get_bookingB | Fetch a specific booking by transaction ID |
| get_bookings_by_dateC | Get bookings within a date range |
| list_eventsA | List all events for the account |
| get_eventC | Get details for a specific event |
| get_event_sessionB | Get event session details by session ID |
| get_event_sectionsB | List sections for an event |
| get_seat_statusC | Get seat status for a session and section |
| get_fundraisingC | Retrieve fundraising pages |
| get_ticket_salesC | Get ticket sales report by period. datePeriod: 1=Day, 2=Week, 3=Month, 4=Year |
| get_booking_salesA | Get booking sales report (max 180 days range) |
| get_event_salesA | Get event sales report (max 180 days range) |
| get_fundraising_salesC | Get fundraising sales report |
| get_scan_attendanceB | Get scan attendance for a session (one scan per ticket) |
| get_scan_allC | Get all scan events for a session |
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
All tools have distinct purposes, covering different resources like transactions, bookings, events, sessions, sales, and scanning. Even though many start with 'get', their targets are clearly differentiated by resource type and context.
14 out of 15 tools follow the 'get_{resource}' pattern. The only exception is 'list_events', which uses 'list' instead of 'get'. This minor inconsistency reduces the score.
15 tools is reasonable for a read-only ticketing API. It covers many query aspects without being overwhelming or too sparse, though a few more could be added for completeness.
The tool set is entirely read-only, lacking any write operations such as creating, updating, or deleting bookings, events, or tickets. This is a significant gap for a ticketing system where transaction processing is expected.