Skip to main content
Glama

Anteos Health — Medical Appointment Booking

by io.github.Anteos-Health

find_next_available

Read-onlyIdempotent

Cherche les prochains créneaux disponibles sur une période, pour un ou plusieurs médecins filtrés par spécialité et/ou ville. À préférer à get_available_slots quand l'utilisateur demande "quand est-ce que X est libre" ou "y a-t-il un RDV disponible cette semaine". Retourne au maximum max_slots créneaux par médecin pour ne pas surcharger le contexte.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoVille (ex: "Paris"). Ignoré si doctor_id est fourni.
daysNoNombre de jours à couvrir depuis from_date (défaut: 7, max: 30)
motif_idNoIdentifiant du motif de consultation (optionnel, obtenu via get_doctor_profile). Adapte la grille de créneaux à la durée du motif.
doctor_idNoChercher uniquement pour ce médecin (obtenu via search_doctors). Court-circuite specialty et city.
from_dateYesDate de début de la recherche au format YYYY-MM-DD
max_slotsNoNombre maximum de créneaux retournés par médecin (défaut: 5, max: 20)
specialtyNoSpécialité médicale (ex: "neurologue", "cardiologue"). Ignoré si doctor_id est fourni.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint true, idempotentHint true, destructiveHint false. The description adds context about returning slots per doctor and limiting to max_slots to avoid context overload, which is valuable beyond annotations.

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 two sentences, front-loaded with purpose and scope, then usage guidance. Every sentence adds value with no redundancy.

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

Completeness3/5

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

While the description covers input well, it does not explain the output format beyond returning slots per doctor. Since there is no output schema, the description should more clearly describe what the returned data contains (e.g., list of slots with doctor info, time format).

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?

Schema coverage is 100% with all parameters described. The description adds cross-tool references (doctor_id from search_doctors, motif_id from get_doctor_profile) and clarifies behavior (city/specialty ignored if doctor_id provided), providing extra value beyond the schema.

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 that the tool searches for next available slots over a period for one or multiple doctors filtered by specialty and/or city. It distinguishes itself from the sibling get_available_slots by specifying when to prefer it.

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?

Explicitly provides usage guidance: prefer this tool over get_available_slots when the user asks 'quand est-ce que X est libre' or 'y a-t-il un RDV disponible cette semaine'. It also notes that it returns max_slots per doctor to avoid overloading context.

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

All Anteos Health — Medical Appointment Booking toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: booking, cancellation, rescheduling, searching for available slots (differentiated by scope), retrieving appointment details, listing appointments, resending tokens, and searching doctors. No ambiguity between tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., book_appointment, find_next_available). This makes the API predictable and easy to use.

Tool Count5/5

With 10 tools, the server is well-scoped for a medical appointment booking system. Each tool serves a necessary function without redundancy or excessive granularity.

Completeness5/5

The tool set covers the full appointment lifecycle: searching doctors and profiles, checking availability, booking, canceling, rescheduling, retrieving appointment details, listing appointments, and resending tokens. No obvious gaps for the intended domain.

Resources