Cup24.it Availability

advanced_search_availability

Read-only

[DETAIL TOOL] Search appointment slots/cards. Use directly when clinic is known, or after search_available_clinics_map selection. Params: city (required), medical_service, doctor, clinic, start_day/end_day (YYYY-MM-DD). Date rules: 'tomorrow/domani' is the day after today; 'next week/prossima settimana' means the next calendar Monday-Sunday week, not tomorrow. If no results with doctor/clinic filters, automatically retries without them. Returns slots with booking_url for checkout (supports pre-filled params: &name=&last_name=&email=&phone=&tax_code=).

Input Schema

TableJSON Schema

Name	Required	Description
`city`	Yes	City name (full or partial, e.g., 'Firenze', 'Milan')
`clinic`	No	Clinic/facility name (full or partial)
`doctor`	No	Doctor name (full or partial, e.g., 'Mario Rossi')
`end_day`	No	Ending date for availability search (YYYY-MM-DD)
`detailed`	No	Return full slot details (default: false, returns summary)
`start_day`	No	Starting date for availability search (YYYY-MM-DD, default: today)
`medical_service`	No	Service name or symptom description (full or partial, e.g., 'Rx Braccio', 'blood test', 'back pain')

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 21, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
Changed1 schema field changedJul 21, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```

Changed1 schema field changedMay 18, 2026

addedInput schema / properties / end_day

Added value: +{
+  "description": "Ending date for availability search (YYYY-MM-DD)",
+  "type": "string"
+}

First observedApr 28, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only annotation, the description discloses important behavioral details: date interpretation rules, automatic retry without filters when no results are found, and the return of booking URLs with pre-fillable parameters. This significantly helps an agent anticipate tool behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-structured, starting with the core purpose, then usage, parameters, date rules, retry behavior, and return value. Each sentence adds necessary information without fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description covers the return value (slots with booking_url) and key behavioral rules thoroughly. It provides enough context for an agent to select and invoke the tool correctly, including parameter formats and fallback logic.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema already describes all parameters (100% coverage), the description adds semantic value by explaining date rule nuances ('tomorrow/domani', 'next week') and the retry behavior. This goes beyond the schema descriptions, though it doesn't add detailed semantics for every parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches appointment slots/cards, using a specific verb and resource. It also sets it apart as a DETAIL TOOL and provides usage context that distinguishes it from sibling tools like search_available_clinics_map.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is given on when to use the tool directly (when clinic is known) and when to use it after search_available_clinics_map selection. This provides clear usage conditions and implies alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cup24.it Availability tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?