Skip to main content
Glama

Search doctors

dt_search_doctors
Read-onlyIdempotent

Search doctors by city, speciality, neighborhood, insurance, visit type, gender, name, or free appointment availability and review matching profiles, fees, and slots to choose care.

Instructions

Search doctors by city, speciality, neighborhood, service tag, name, gender, insurance and visit type.

Cards have the hash id for dt_doctor; online prices only in dt_doctor. Next: dt_doctor -> dt_free_slots.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dt_search_doctors"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity slug from dt_cities, e.g. 'tehran'. Omit for the whole country.
nameNoPersian name (part is enough), e.g. 'پرآذران'.
pageNo1-based page number.
sortNodefault = site ranking (sponsored first).default
limitNoDoctors per page.
genderNoOnly male or only female doctors.
near_latNoLatitude of a point in Iran, e.g. 35.7575.
near_lonNoLongitude of a point in Iran, e.g. 51.4100.
specialityNoSlug from dt_specialities, e.g. 'cardiologist'.
visit_typeNoinstant = on-call phone/text now.
service_tagNoTag slug from dt_suggest, e.g. 'echocardiography'.
neighborhoodNoSlug from dt_neighborhoods (needs city), e.g. 'pasdaran'.
has_free_slotNoOnly doctors with a free appointment slot.
insurance_idsNoIds from dt_insurances (any), e.g. [1].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed46 schema fields changedv0.5.0
    • removedInput schema / properties / city / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 80,
      -    "pattern": "^[a-z0-9][a-z0-9_-]*$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / city / maxLength
      Added value: +80
    • addedInput schema / properties / city / pattern
      Added value: +"^[a-z0-9][a-z0-9_-]*$"
    • addedInput schema / properties / city / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / gender / anyOf
      Removed value: -[
      -  {
      -    "enum": [
      -      "male",
      -      "female"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / gender / enum
      Added value: +[
      +  "male",
      +  "female"
      +]
    • addedInput schema / properties / gender / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / insurance_ids / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "maximum": 9999,
      -      "minimum": 1,
      -      "type": "integer"
      -    },
      -    "maxItems": 10,
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / insurance_ids / description
      Previous value: -"Insurance ids from dt_insurances (any of them), e.g. [1]. Few doctors list insurances."New value: +"Ids from dt_insurances (any), e.g. [1]."
    • addedInput schema / properties / insurance_ids / items
      Added value: +{
      +  "maximum": 9999,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / insurance_ids / maxItems
      Added value: +10
    • addedInput schema / properties / insurance_ids / type
      Added value: +[
      +  "array",
      +  "null"
      +]
    • changedInput schema / properties / limit / description
      Previous value: -"Doctors per page (about 1 KB each)."New value: +"Doctors per page."
    • removedInput schema / properties / name / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 80,
      -    "minLength": 2,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / name / description
      Previous value: -"Doctor's name in Persian (part is enough), e.g. 'پرآذران'."New value: +"Persian name (part is enough), e.g. 'پرآذران'."
    • addedInput schema / properties / name / maxLength
      Added value: +80
    • addedInput schema / properties / name / minLength
      Added value: +2
    • addedInput schema / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / near_lat / anyOf
      Removed value: -[
      -  {
      -    "maximum": 40,
      -    "minimum": 24,
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / near_lat / maximum
      Added value: +40
    • addedInput schema / properties / near_lat / minimum
      Added value: +24
    • addedInput schema / properties / near_lat / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / near_lon / anyOf
      Removed value: -[
      -  {
      -    "maximum": 64,
      -    "minimum": 44,
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / near_lon / maximum
      Added value: +64
    • addedInput schema / properties / near_lon / minimum
      Added value: +44
    • addedInput schema / properties / near_lon / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / neighborhood / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 80,
      -    "pattern": "^[a-z0-9][a-z0-9_-]*$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / neighborhood / description
      Previous value: -"Neighborhood slug from dt_neighborhoods, with city only, e.g. 'pasdaran'."New value: +"Slug from dt_neighborhoods (needs city), e.g. 'pasdaran'."
    • addedInput schema / properties / neighborhood / maxLength
      Added value: +80
    • addedInput schema / properties / neighborhood / pattern
      Added value: +"^[a-z0-9][a-z0-9_-]*$"
    • addedInput schema / properties / neighborhood / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / service_tag / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 80,
      -    "pattern": "^[a-z0-9][a-z0-9_-]*$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / service_tag / description
      Previous value: -"Service or symptom tag slug from dt_suggest, e.g. 'echocardiography'."New value: +"Tag slug from dt_suggest, e.g. 'echocardiography'."
    • addedInput schema / properties / service_tag / maxLength
      Added value: +80
    • addedInput schema / properties / service_tag / pattern
      Added value: +"^[a-z0-9][a-z0-9_-]*$"
    • addedInput schema / properties / service_tag / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedInput schema / properties / sort / description
      Previous value: -"default = site ranking (sponsored first); popular = reviews and recommend rate."New value: +"default = site ranking (sponsored first)."
    • removedInput schema / properties / speciality / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 80,
      -    "pattern": "^[a-z0-9][a-z0-9_-]*$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / speciality / description
      Previous value: -"Speciality slug from dt_specialities or dt_suggest, e.g. 'cardiologist'."New value: +"Slug from dt_specialities, e.g. 'cardiologist'."
    • addedInput schema / properties / speciality / maxLength
      Added value: +80
    • addedInput schema / properties / speciality / pattern
      Added value: +"^[a-z0-9][a-z0-9_-]*$"
    • addedInput schema / properties / speciality / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / visit_type / anyOf
      Removed value: -[
      -  {
      -    "enum": [
      -      "office",
      -      "phone",
      -      "text",
      -      "video",
      -      "instant",
      -      "any_online"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / visit_type / description
      Previous value: -"Only doctors offering this visit; instant = on-call phone/text now."New value: +"instant = on-call phone/text now."
    • addedInput schema / properties / visit_type / enum
      Added value: +[
      +  "office",
      +  "phone",
      +  "text",
      +  "video",
      +  "instant",
      +  "any_online"
      +]
    • addedInput schema / properties / visit_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed18 schema fields changedv0.3.0
    • removedInput schema / properties / city / title
      Removed value: -"City"
    • removedInput schema / properties / gender / title
      Removed value: -"Gender"
    • removedInput schema / properties / has_free_slot / title
      Removed value: -"Has Free Slot"
    • removedInput schema / properties / insurance_ids / title
      Removed value: -"Insurance Ids"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / name / title
      Removed value: -"Name"
    • removedInput schema / properties / near_lat / title
      Removed value: -"Near Lat"
    • removedInput schema / properties / near_lon / title
      Removed value: -"Near Lon"
    • removedInput schema / properties / neighborhood / title
      Removed value: -"Neighborhood"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / service_tag / title
      Removed value: -"Service Tag"
    • changedInput schema / properties / sort / description
      Previous value: -"default = site ranking (sponsored first), popular = review count and recommend rate, earliest = soonest free slot, most_booked = most bookings."New value: +"default = site ranking (sponsored first); popular = reviews and recommend rate."
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / properties / speciality / title
      Removed value: -"Speciality"
    • changedInput schema / properties / visit_type / description
      Previous value: -"Only doctors offering this visit: office (in person), phone, text (chat), video, instant (on-call phone/text now), any_online."New value: +"Only doctors offering this visit; instant = on-call phone/text now."
    • removedInput schema / properties / visit_type / title
      Removed value: -"Visit Type"
    • removedInput schema / title
      Removed value: -"dt_search_doctorsArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dt_search_doctorsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuine value beyond that: cards carry a hash `id` usable with dt_doctor, and online prices are NOT in search results (only in dt_doctor), which tells the agent the result set is a lightweight projection. It does not disclose result-count/pagination totals or whether multiple filters combine with AND semantics.

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?

Two tight blocks with the purpose front-loaded and the workflow note last; no filler text. The second paragraph is arguably too compressed — 'Cards have the hash `id` for dt_doctor; online prices only in dt_doctor' is telegraphic enough to need a second read.

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?

For a 14-parameter, zero-required search tool with no output schema, the description covers purpose, the key output caveat (id for dt_doctor, no online prices) and the follow-up call chain. It falls short on how filters interact when combined, slug-resolution prerequisites, and what an empty result means, but the rich schema covers the mechanical parameter detail.

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 every one of the 14 parameters is already documented with slug formats, enums and ranges. The description's filter enumeration largely restates schema fields (and omits near_lat/near_lon, sort, page, limit, has_free_slot), adding no syntax or interaction semantics beyond the schema. Baseline 3 applies.

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?

States a specific verb ('Search') and resource ('doctors') and enumerates the filter dimensions: city, speciality, neighborhood, service tag, name, gender, insurance, visit type. An agent can immediately distinguish this from dt_search_centers (centers) and dt_specialities/dt_cities (reference lookups) 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit next-step routing ('Next: dt_doctor -> dt_free_slots'), which tells the agent how this tool fits a workflow. However, it gives no when-not guidance — nothing says when to use dt_search_centers instead for a location-based lookup, nor prerequisites such as resolving slugs via dt_cities/dt_specialities before filtering.

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