Skip to main content
Glama

Anteos Health — Medical Appointment Booking

by io.github.Anteos-Health
OverviewDiscussionsAdmin

book_appointment

Prend un rendez-vous pour un patient chez un médecin Anteos. Le rendez-vous est immédiatement confirmé dans l'agenda du médecin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate du rendez-vous au format YYYY-MM-DD (ex: "2026-04-20")
timeYesHeure du rendez-vous au format HH:MM (ex: "14:30")
motifNoMotif de la consultation en texte libre (optionnel, ex: "Suivi traitement", "Renouvellement ordonnance")
motif_idNoIdentifiant du motif de consultation (optionnel, obtenu via get_doctor_profile). Détermine la durée du RDV et est enregistré dans l'agenda du médecin.
doctor_idYesIdentifiant du médecin (obtenu via search_doctors)
patient_dobYesDate de naissance du patient au format YYYY-MM-DD. Obligatoire.
patient_sexYesSexe du patient : M (Masculin), F (Féminin) ou autre. Obligatoire.
patient_emailYesEmail du patient — OBLIGATOIRE. Utilisé pour l'envoi de la confirmation et des rappels de rendez-vous.
patient_phoneNoTéléphone du patient (optionnel — format: 0612345678 ou +33612345678)
patient_lastnameYesNom de famille du patient (en majuscules de préférence)
patient_firstnameYesPrénom du patient
send_confirmation_emailNoEnvoyer un email de confirmation au patient avec des liens de gestion du RDV. Défaut: true. Passer false si votre plateforme envoie sa propre confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / motif / description
      Previous value: -"Motif de la consultation (optionnel, ex: \"Suivi traitement\", \"Renouvellement ordonnance\")"New value: +"Motif de la consultation en texte libre (optionnel, ex: \"Suivi traitement\", \"Renouvellement ordonnance\")"
    • addedInput schema / properties / motif_id
      Added value: +{
+  "description": "Identifiant du motif de consultation (optionnel, obtenu via get_doctor_profile). Détermine la durée du RDV et est enregistré dans l'agenda du médecin.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / patient_dob / description
      Previous value: -"Date de naissance du patient au format YYYY-MM-DD. Fortement recommandée pour éviter les confusions entre homonymes."New value: +"Date de naissance du patient au format YYYY-MM-DD. Obligatoire."
    • changedInput schema / required
      Previous value: -[
-  "doctor_id",
-  "date",
-  "time",
-  "patient_lastname",
-  "patient_firstname",
-  "patient_email",
-  "patient_sex"
-]New value: +[
+  "doctor_id",
+  "date",
+  "time",
+  "patient_lastname",
+  "patient_firstname",
+  "patient_email",
+  "patient_sex",
+  "patient_dob"
+]
  3. Changed3 schema fields changed
    • changedInput schema / properties / patient_sex / description
      Previous value: -"Sexe du patient : M (Masculin) ou F (Féminin). Défaut: M"New value: +"Sexe du patient : M (Masculin), F (Féminin) ou autre. Obligatoire."
    • changedInput schema / properties / patient_sex / enum
      Previous value: -[
-  "M",
-  "F"
-]New value: +[
+  "M",
+  "F",
+  "autre"
+]
    • changedInput schema / required
      Previous value: -[
-  "doctor_id",
-  "date",
-  "time",
-  "patient_lastname",
-  "patient_firstname",
-  "patient_email"
-]New value: +[
+  "doctor_id",
+  "date",
+  "time",
+  "patient_lastname",
+  "patient_firstname",
+  "patient_email",
+  "patient_sex"
+]
  4. Changed1 schema field changed
    • addedInput schema / properties / send_confirmation_email
      Added value: +{
+  "default": true,
+  "description": "Envoyer un email de confirmation au patient avec des liens de gestion du RDV. Défaut: true. Passer false si votre plateforme envoie sa propre confirmation.",
+  "type": "boolean"
+}
  5. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations indicate a mutation (readOnlyHint false, idempotentHint false). The description adds that the appointment is 'immediately confirmed,' which is useful but does not disclose potential conflicts or error handling beyond that.

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 the main action, and contains no redundant information. Every word is necessary.

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?

Given the tool has 12 parameters and no output schema, the description covers the core behavior but does not address typical flow, required fields summary, or what the agent should expect after calling.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no extra parameter-level meaning beyond what's in 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 states a specific action: booking an appointment for a patient with an Anteos doctor. It clearly distinguishes from sibling tools like cancel_appointment or reschedule_appointment.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives. While it implies booking, it lacks context like prerequisites (e.g., needing doctor_id from search_doctors) or when not to use it.

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
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