Skip to main content
Glama
sepehr071

doctoreto-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Free appointment slots

dt_free_slots
Read-onlyIdempotent

Find available appointment times for a chosen consultation up to a month ahead. Returns only days with open slots and Tehran-local start times.

Instructions

Free appointment times of one service (office visit, phone/video call, clinic offer, lab admission).

Returns only days with free times: date, weekday, Jalali date and free start times (HH:MM, Tehran local). Past times today are dropped. bookable_until is the last day opened (often ~30 days ahead). Text consultations usually have no slots.

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to check from start_date.
start_dateNoFirst day, Gregorian YYYY-MM-DD; default today (Tehran), e.g. '2026-10-14'.
consultation_idYesConsultation id from dt_doctor services[], dt_center bookable[] or dt_offer variants[], e.g. 1943.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • changedInput schema / properties / consultation_id / description
      Previous value: -"Consultation id of one service, from dt_doctor services[], dt_center services[] or dt_offer variants[], e.g. 1943."New value: +"Consultation id from dt_doctor services[], dt_center bookable[] or dt_offer variants[], e.g. 1943."
    • removedInput schema / properties / consultation_id / title
      Removed value: -"Consultation Id"
    • removedInput schema / properties / days / title
      Removed value: -"Days"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
    • removedInput schema / title
      Removed value: -"dt_free_slotsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dt_free_slotsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely useful behavior beyond that: only days with free times are returned, past times today are dropped, `bookable_until` is the last opened day (~30 days), times are Tehran local, and text consultations typically yield nothing. It stops short of auth or error behavior.

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?

Purpose is front-loaded in the first sentence, then return fields and caveats follow in an efficient block with no filler. Slightly dense parenthetical enumeration and a dangling sentence on text consultations keep it from being maximally tight.

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 no output schema, the description carries the return-value burden and does it well (date, weekday, Jalali date, free start times, bookable_until). It omits invalid-consultation_id or empty-result behavior, but for a read-only listing tool the essential context is present.

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 baseline is 3. The description reinforces the Tehran-local time convention and the free-slot window but adds little syntax or defaulting detail beyond the schema's own descriptions of days, start_date, and consultation_id.

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 first sentence names a specific resource and verb-mapping ('Free appointment times of one service') and enumerates the service variants it covers, which no sibling tool does. An agent can distinguish it from dt_doctor (service listing) or dt_center without opening the schema.

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?

Usage is only implied: the description notes text consultations usually have no slots and the schema says the consultation_id comes from dt_doctor/dt_center/dt_offer, but that wiring lives in the schema, not the description. There is no explicit when-to-use/when-not statement or named alternative for slot discovery.

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

Deploy Server

Other Tools