Skip to main content
Glama
Sign In

Anteos Health — Medical Appointment Booking

by io.github.Anteos-Health
OverviewDiscussionsAdmin

get_available_slots

Read-onlyIdempotent

Retourne les créneaux disponibles pour un médecin à une date donnée. À appeler avant book_appointment pour proposer des options concrètes au patient plutôt que de réserver à l'aveugle.

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": {
      "doctor_id": "<doctor_id>",
      "date": "<date>"
    },
    "name": "get_available_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate au format YYYY-MM-DD (ex: "2026-05-10")
motif_idNoIdentifiant du motif de consultation (optionnel, obtenu via get_doctor_profile). Adapte la grille de créneaux à la durée du motif.
doctor_idYesIdentifiant du médecin (obtenu via search_doctors)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / motif_id
      Added value: +{
+  "description": "Identifiant du motif de consultation (optionnel, obtenu via get_doctor_profile). Adapte la grille de créneaux à la durée du motif.",
+  "type": "string"
+}
  2. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds the usage context but does not elaborate on output format or edge cases like no slots, which is acceptable given the 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?

Two sentences that efficiently convey purpose and usage guidance. No redundant words; each sentence adds value.

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

Completeness4/5

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

For a simple read-only slot query tool with no output schema, the description covers the core functionality and timing relative to booking. It lacks explicit mention of the output format (list of time slots), but the tool name implies this, making it largely complete.

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 coverage is 100% with parameter descriptions for all three parameters. The description does not add additional meaning beyond what the schema provides, so baseline score of 3 applies.

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 it returns available slots for a doctor on a given date, using specific verb 'retourne' and resource 'créneaux disponibles'. It distinguishes itself from the sibling tool book_appointment by noting it should be called before booking.

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

Usage Guidelines4/5

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

The description explicitly instructs to call this tool before book_appointment to offer concrete options, providing clear context. It does not explicitly mention when not to use it, but the guidance is sufficient for selecting the tool.

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