Skip to main content
Glama

mcp

by clinic.enmente

get_availability

Read-only

Return the next available consultation slot (when fresh) for a specific professional, plus the URL to send the patient to. Prefer profile_url — the professional's page on enmente.clinic, which carries their credentials and its own booking button. IMPORTANT: professional_slug is NOT derivable from the person's name — slugs are inconsistent (e.g. "raul-riquelme-pena", "dr-raul-riquelme-vejar", "dra-natacha-loubies-munoz", "ps-esteban-caamano-gonzalez") and there is no naming rule to construct one from. Always obtain the exact slug first from find_professional or list_professionals — never invent or guess it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
days_aheadNo
professional_slugYesProfessional slug, e.g. "raul-riquelme-pena"

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior, so the bar is lower. The description adds useful context about the non-derivability of slugs and the preferred URL, without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main purpose, followed by important usage caveats. While slightly verbose with examples, every sentence adds value and the structure is logical.

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?

Given no output schema, the description covers the core return values (slot and URL) and the necessary prerequisite step. It lacks details about edge cases like no availability or the exact response format, but is sufficiently complete for the typical use case.

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?

The description adds substantial meaning to professional_slug, explaining its non-deterministic nature and how to obtain it—far beyond the schema example. However, days_ahead is not explained, leaving its semantics partially implicit despite schema constraints.

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 the verb ('Return') and resource ('next available consultation slot... plus the URL'), and distinguishes itself from siblings like find_professional and list_professionals by focusing on availability and the patient URL.

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?

It explicitly instructs to obtain the professional_slug from find_professional or list_professionals, warns against guessing, and explains when to prefer profile_url. This provides clear contextual usage guidance and differentiates from alternatives.

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

All mcp 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
Disambiguation4/5

Most tools have clearly distinct purposes: joining, finding professionals, checking availability, listing professionals, self-assessments, and blog search. The only potential confusion is between find_professional and list_professionals, but the descriptions clarify that one is for natural-language queries and the other for structured filters.

Naming Consistency4/5

Five tools follow a consistent verb_noun pattern (find_professional, get_availability, list_professionals, list_self_assessments, search_blog), making the set predictable. The outlier is about_joining_enmente, which is a descriptive phrase rather than a verb_noun construction, creating a minor deviation.

Tool Count5/5

Six tools is an appropriate size for this server's scope: professional discovery, scheduling, self-assessment resources, and blog content. Each tool covers a distinct aspect of the platform without redundancy, and the count is neither too thin nor overwhelming.

Completeness4/5

The core workflows are covered: finding/listing professionals, checking availability, accessing self-assessments, and searching blog articles. Minor gaps exist, such as no direct 'get_professional' endpoint (though find/list already return detailed information), and booking is handled externally via URLs, but these are reasonable workarounds.

Resources