get_date_night
Use this when the user wants an evening for two. Returns a flat ranked list of experiences (search rows) with romantic-tagged rows promoted and out-of-season products dropped, not a structured pre-dinner/dinner/show arc. Promotion is a re-rank, not a filter, so rows are not guaranteed couples-only. date selects which season counts as current; budget is accepted but NOT yet applied. Compose the evening yourself (search_by_mood with mood 'romantic' can bias the pool further).
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": {
"city": "<city>"
},
"name": "get_date_night"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City slug. | |
| date | No | Optional ISO date (YYYY-MM-DD). | |
| budget | No | Budget band. 'low' = under 100 per person, 'medium' = 100-200, 'high' = 200+. In the listed currency. | |
| format | No | Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces. | json |
| language | No | BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| detail | No | ||
| message | No | ||
| results | No | ||
| error_type | No | ||
| pagination | No | ||
| request_id | No | ||
| experiences | No | ||
| _normalization | No | ||
| schema_version | No |