Skip to main content
Glama

Anteos Health — Medical Appointment Booking

by io.github.Anteos-Health

search_doctors

Read-onlyIdempotent

Recherche des médecins Anteos par spécialité et/ou ville. Retourne les médecins avec disponibilités, secteur conventionnement et informations pratiques. Utilisez get_doctor_profile avec le champ id pour obtenir le profil complet d'un médecin (avis patients, diplômes, langues, tarifs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoVille où rechercher (ex: "Paris", "Lyon")
limitNoNombre maximum de résultats par page (défaut: 10, max: 50)
offsetNoDécalage pour la pagination (défaut: 0). Utiliser limit+offset pour naviguer au-delà de la première page.
specialtyNoSpécialité médicale (ex: "médecin généraliste", "dermatologue", "cardiologue")
available_fromNoSi fourni, ne retourne que les médecins ayant au moins un créneau libre à partir de cette date (YYYY-MM-DD). Utile pour filtrer d'emblée sur la disponibilité.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds value by listing returned fields (disponibilités, secteur conventionnement, informations pratiques). No contradictions.

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 concise sentences: first states purpose, second gives clear follow-up action. No wasted words. Front-loaded with key information.

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?

With 5 optional parameters and no output schema, the description adequately covers the tool's purpose and return content, but lacks details on pagination behavior beyond limit/offset schema. Still sufficient for a search tool.

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 baseline is 3. Description does not add semantic value beyond what schema provides for parameters. It only mentions specialty and city as filters, which are already documented.

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?

Description clearly states the verb 'Recherche' (search) and resource 'médecins Anteos' with filters 'par spécialité et/ou ville'. It distinguishes from sibling tool 'get_doctor_profile' by referencing it explicitly for full profiles.

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?

Description provides explicit guidance to use 'get_doctor_profile' for detailed information, but does not explicitly state when not to use this tool. However, the context is clear for when to use 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