Skip to main content
Glama

Free appointment slots

dt_free_slots
Read-onlyIdempotent

Returns free appointment times for a selected service, listing only days with available slots and the last bookable date.

Instructions

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

Returns only days with free times (HH:MM, Tehran local). bookable_until is the last day opened. Text consultations usually have no slots.

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": {
      "consultation_id": "<consultation_id>"
    },
    "name": "dt_free_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays to check.
start_dateNoGregorian YYYY-MM-DD; default today (Tehran).
consultation_idYesId from dt_doctor services[], dt_center bookable[] or dt_offer variants[].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.0
    • changedInput schema / properties / consultation_id / description
      Previous value: -"Consultation id from dt_doctor services[], dt_center bookable[] or dt_offer variants[], e.g. 1943."New value: +"Id from dt_doctor services[], dt_center bookable[] or dt_offer variants[]."
    • changedInput schema / properties / days / description
      Previous value: -"Number of days to check from start_date."New value: +"Days to check."
    • removedInput schema / properties / start_date / anyOf
      Removed value: -[
      -  {
      -    "format": "date",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / start_date / description
      Previous value: -"First day, Gregorian YYYY-MM-DD; default today (Tehran), e.g. '2026-10-14'."New value: +"Gregorian YYYY-MM-DD; default today (Tehran)."
    • addedInput schema / properties / start_date / format
      Added value: +"date"
    • addedInput schema / properties / start_date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. 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
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds behavior the annotations cannot: results are filtered to days that actually have free times, times are HH:MM in Tehran local, and `bookable_until` marks the last bookable day. It does not mention error behavior for an invalid consultation_id or any rate limiting, so it is not fully exhaustive.

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?

Three compact sentences with the purpose front-loaded, followed by return behavior and then a practical caveat; every sentence carries information. Minor cost: 'bookable_until is the last day opened' is terse to the point of ambiguity about which object the field belongs to.

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 only 3 flat parameters, full schema coverage, and no output schema, the description carries the return-value burden and largely discharges it by describing the day-level filtering and time format. It stops short of describing the exact response shape (how days are keyed) or the empty-result case, which would matter for an agent parsing the output.

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 days, start_date and consultation_id are all documented in the schema itself, and the 3 baseline applies. The description contributes the concept of scoping to 'one service' and the Tehran timezone expectation, but adds no format or boundary detail beyond the schema. Nothing is missing, but little is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource: free appointment times for a single service, and enumerates the service kinds covered (office visit, phone/video call, clinic offer, lab admission). It is clearly distinct from the sibling tools, which all deal with doctors, centers, offers, or reference data rather than availability. It loses a point only because it is a noun phrase rather than an explicit verb+resource statement.

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?

There is no explicit when-to-use/when-not-to-use framing and no named alternative among the siblings (dt_suggest or dt_offer would be the obvious candidates for scheduling). Usage is only implied by the service enumeration. The caveat that text consultations usually have no slots is a genuine piece of selection guidance, which keeps this above a 2.

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