create_alert
Set up an email alert for the user: LayUp watches for NEW matching slots (e.g. a cancellation freeing up a peak court) and emails them when one appears. Use when the user can't find a slot now and wants to be notified, or asks to 'monitor'/'watch'/'let me know when'. Requires their email. NARROW IT FIRST. An alert with no venues attached matches hundreds of slots, so the emails read as a dump rather than an alert: of 20 such alerts, 1 was ever confirmed and 8 died unconfirmed at the send cap. Call this without venue_names and the tool will NOT create an alert — it returns the venues LayUp covers in that area so you can ask the user which ones they want, and prompts for the days and times that suit them. Then call again with their answers. LayUp does the watching; the notification arrives by email, not in this chat.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"email": "<email>"
},
"name": "create_alert"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| area | No | Where to watch, resolved geographically: a borough ('Hackney'), a neighbourhood ('Maida Vale'), a region ('North London'), or a postcode ('W9 2RF', 'SE1'). A postcode is the most precise option when the user gives one. NOT a venue name — to watch a specific venue use venue_names. Omit for all London. | |
| Yes | The user's REAL email address, as given by them (required — alerts are emailed here). Never invent, guess or substitute a placeholder like user@example.com; if you don't have it, ask the user first. | ||
| sport | No | One of Football, Tennis, Squash, Padel, Swimming. Omit for any. | |
| time_to | No | Latest London time-of-day, 'HH:MM'. | |
| max_price | No | Only alert on slots at or under this GBP price. | |
| time_from | No | Earliest London time-of-day, 'HH:MM' (e.g. '18:00'). | |
| venue_names | No | Pin the alert to specific venues BY NAME, exactly as shown in search results (e.g. ["Hay's Galleria", "Padel Box"]). Use this whenever the user names venues — the server resolves names to the right venue(s). Prefer this over venue_slugs. | |
| venue_slugs | No | Pin the alert to specific venues by their exact venue_slug (only if you already have slug values from search_slots). For most cases use venue_names instead. Omit for any venue. | |
| days_of_week | No | Only alert on these days (e.g. ['Sat','Sun'] for weekends). The alert is standing — it keeps watching these days every week until the user unsubscribes. Omit for any day. | |
| all_venues_in_area | No | Set true ONLY after the user has explicitly said they want every venue in the area rather than a chosen few. Without venue_names the tool refuses and hands you the venue list to offer them — area-wide alerts match hundreds of slots, are never confirmed and lapse unused. |