Skip to main content
Glama

Anteos Health — Medical Appointment Booking

by io.github.Anteos-Health

reschedule_appointment

Reporte un rendez-vous existant vers un nouveau créneau. L'opération est atomique : l'ancien RDV est annulé et le nouveau est créé en une seule transaction, évitant qu'un autre agent prenne le créneau cible entre les deux. Un nouveau appointment_token est émis — l'ancien est révoqué définitivement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
new_dateYesNouvelle date au format YYYY-MM-DD
new_timeYesNouvelle heure au format HH:MM
appointment_idYesIdentifiant du rendez-vous à reporter
appointment_tokenYesToken de sécurité reçu lors de la réservation initiale

TDQS

A3.6/5.0
Behavior1/5

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

La description révèle que l'ancien RDV est annulé et l'ancien token révoqué, ce qui est destructif. Or, l'annotation destructiveHint: false indique le contraire, créant une contradiction flagrante.

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?

Deux phrases concises et informatives, sans verbiage inutile. L'information clé (atomicité, changement de jeton) est en tête.

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?

L'opération de report est bien décrite avec ses implications (atomicité, révocation de jeton). Cependant, l'absence de schéma de sortie et la non-mention du format de réponse laissent une légère lacune.

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?

Le schéma couvre 100 % des paramètres, donc le niveau de base est 3. La description n'ajoute pas de sémantique supplémentaire pour les paramètres individuels.

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?

Le verbe 'Reporte' et le complément 'rendez-vous existant vers un nouveau créneau' spécifient clairement l'action et la ressource. La distinction avec les outils frères est faite via l'atomicité et le renouvellement du jeton.

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?

La description indique quand utiliser l'outil (pour reporter un rendez-vous) et mentionne l'avantage de l'atomicité, mais elle ne précise pas explicitement quand ne pas l'utiliser ni ne donne d'alternatives.

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