cup24-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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cup24_searchA | Search cup24.it by name: healthcare services (exams, visits, lab tests, check-up packages), clinics and doctors. Search in Italian. Returns ids for the other tools:
|
| cup24_search_citiesA | Find Italian cities, and zones inside big cities, covered by cup24.it and return their slugs. Use the returned slug as city in cup24_get_availability. Zones narrow the search, e.g. "firenze-zona-campo-di-marte". Examples: "firenze", "milano", "sesto fiorentino". |
| cup24_get_availabilityA | Real-time availability and prices on cup24.it, from private clinics. Pass one of:
Returns slots: one per clinic and day, with that day's free times, service, price in EUR (full_price_eur and price_note on promotions), clinic, rating, address, coordinates, distance in km from the city centre, doctor, slot_id for cup24_get_slot_times, and booking_url to book on the website. Results come in chronological pages: when slots is not empty, call again with page=next_page for later dates. |
| cup24_get_slot_timesA | Exact bookable times for a slot from cup24_get_availability, day by day: the slot's day, then the next available days of the same clinic and doctor, as in the website's "Scegli data e ora" picker. For lab tests the only entry describes the walk-in window (e.g. "Esecuzione prelievi: il Martedì dalle 07:00 alle 09:00"). To book, open the slot's booking_url. |
| cup24_get_service_infoA | What a service is and what it costs across Italy, from its cup24.it page: FAQ (what it is for, how to prepare, fasting, duration, contraindications), min and max price per major city, and for check-up packages the lab tests included. Use cup24_get_availability for real-time prices and dates. |
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 5 tools
Each tool targets a distinct step of a clear pipeline: text search, city/zone lookup, day-level availability, exact slot times, and static service encyclopedia info. The descriptions explicitly cross-reference which tool's output feeds the next, and the availability vs. slot_times split (day overview vs. exact times) is clearly delineated.
All five tools use the same cup24_ prefix followed by a consistent snake_case verb_noun pattern (search, search_cities, get_availability, get_slot_times, get_service_info). No mixing of conventions or casing styles.
Five tools map exactly onto the domain's workflow stages with no redundant or filler entries. This is a well-scoped set well within the 3-15 range, and each tool earns its place.
The surface covers discovery, location resolution, availability, exact times, and service education, which is a coherent end-to-end decision flow. The only gap is that booking is delegated to an external booking_url rather than an in-server booking/cancellation tool, which is a reasonable but real omission.