Padel Finder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 3000 |
| NODE_ENV | No | Node environment | development |
| GEOCODING_API_KEY | No | API key for geocoding (if needed) | |
| GEOCODING_PROVIDER | No | Geocoding provider | nominatim |
| PLAYTOMIC_API_BASE | No | Playtomic API base URL | https://api.playtomic.io/v1 |
| PLAYTOMIC_SPORT_ID | No | Sport ID | 1 |
| PLAYTOMIC_CLIENT_ID | Yes | Playtomic API client ID | |
| PLAYTOMIC_CLIENT_SECRET | Yes | Playtomic API client secret | |
| PLAYTOMIC_RATE_LIMIT_PER_MIN | No | Rate limit per minute | 1 |
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 |
|---|---|
| find_nearby_courtsA | Find padel courts and venues near a given location. Returns a list of venues with their addresses and distances. |
| check_availabilityA | Check available padel court time slots at a specific venue. Returns slots with weather info, booking links, and calendar links. |
| find_available_gamesB | Find the nearest available padel games based on your location and preferred time. Returns slots with weather info, booking links, and calendar links. |
| compare_pricesA | Compare padel court prices across multiple venues. Shows cheapest options first. |
| set_availability_alertA | Set up a persistent alert for when a preferred time slot becomes available. Alerts are saved to disk and support webhook notifications. |
| list_availability_alertsB | List all availability alerts (active and past). |
| cancel_availability_alertB | Cancel an existing availability alert. |
| get_venue_detailsB | Get detailed information about a specific padel venue including address, contact info, courts, and amenities. |
| search_by_durationA | Find padel courts available for a specific duration (e.g., exactly 90 minutes). Filters out slots that don't match your duration requirement. |
| save_favorite_venueA | Save a venue to your favorites for quick access. You can optionally give it a nickname. |
| remove_favorite_venueB | Remove a venue from your favorites. |
| list_favorite_venuesA | List all your saved favorite venues. |
| quick_book_checkB | Quick check: See availability at all your favorite venues for a specific time. Perfect for "Can I play tonight?" |
| get_weekly_availabilityA | View padel court availability across multiple days (up to a week). Includes weather forecast for planning. |
| find_cheapest_timeC | Find the cheapest available padel court slots in your area. Results are sorted by price (lowest first). |
| get_peak_hoursA | Analyze availability patterns at a venue to find peak and off-peak hours. Shows when courts are typically busy or quiet. |
| book_courtC | Start booking process for a padel court slot with interactive checkout wizard. Opens a multi-step checkout flow. |
| test_hello_worldB | Test widget rendering and interactivity with a simple Hello World widget |
| test_slot_cardsB | Test slot cards widget with mock booking data |
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 19 tools
Several tools overlap in purpose, especially those related to availability checking (check_availability, find_available_games, find_cheapest_time, quick_book_check, get_weekly_availability). While descriptions differentiate them, an agent may still struggle to select the correct one. The inclusion of test tools adds further ambiguity.
Most tools follow a clear verb_noun pattern (e.g., book_court, check_availability, save_favorite_venue). The only deviation is quick_book_check, which uses an adjective+noun+noun structure. Overall, naming is predictable and consistent.
With 19 tools, the count is on the higher side for a focused padel finder server. The inclusion of two test-only tools (test_hello_world, test_slot_cards) that are unrelated to the core domain makes the set feel bloated. Removing those would bring it to a more reasonable 17.
The tool surface covers venue discovery, availability, pricing, favorites, and alerts well. However, the booking lifecycle is incomplete: there is only book_court (which starts a process) but no tool to confirm, cancel, or view bookings. This gap could cause agent failures.