Skip to main content
Glama
Sign In
doctoreto-mcp

doctoreto-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search clinic offers

dt_search_offers
Read-onlyIdempotent

Search fixed-price clinic offers and packages (ultrasound, laser, dental, check-ups) by city, doctor, speciality, or price range.

Instructions

Search clinic offers: fixed-price procedures and packages (ultrasound, laser, dental, check-ups).

Cards give price and discounted price (Toman), pay_online (the deposit when payment is deposit_online, the rest at the place) and the default consultation_id for dt_free_slots. No sort. limit cuts the upstream page (on_page items): raise it to see the rest, page jumps a whole page. Next: dt_offer, dt_free_slots, dt_reviews(of='offer').

Input Schema

NameRequiredDescriptionDefault
cityNoCity slug from dt_cities, e.g. 'tehran'.
pageNo1-based page number.
limitNoOffers to return from the page (the API pages by about 40).
queryNoService in Persian, e.g. 'سونوگرافی' or 'لیزر'.
centerNoOnly offers at this place (hash id), e.g. 'ZWpOLy'.
doctorNoOnly offers of this doctor (hash id or page URL).
max_priceNoMaximum price in Toman, e.g. 2000000.
min_priceNoMinimum price in Toman, e.g. 1000000.
specialityNoSpeciality slug, e.g. 'cardiologist'.
service_tagNoService tag slug, e.g. 'rhinoplasty'.
neighborhoodNoNeighborhood slug, e.g. 'pasdaran'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv0.3.0
    • removedInput schema / properties / center / title
      Removed value: -"Center"
    • removedInput schema / properties / city / title
      Removed value: -"City"
    • changedInput schema / properties / doctor / anyOf
      Previous value: -[
-  {
-    "description": "Doctor hash id from a search ('xqbEWZ') or the doctor's page URL ('https://doctoreto.com/doctor/dr-kambiz-parazaran/xqbEWZ'). The slug alone cannot be resolved.",
-    "maxLength": 300,
-    "minLength": 6,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Doctor hash id ('xqbEWZ') or page URL ('https://doctoreto.com/doctor/dr-kambiz-parazaran/xqbEWZ').",
+    "maxLength": 300,
+    "minLength": 6,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / doctor / title
      Removed value: -"Doctor"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / max_price / title
      Removed value: -"Max Price"
    • removedInput schema / properties / min_price / title
      Removed value: -"Min Price"
    • removedInput schema / properties / neighborhood / title
      Removed value: -"Neighborhood"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / service_tag / title
      Removed value: -"Service Tag"
    • removedInput schema / properties / speciality / title
      Removed value: -"Speciality"
    • removedInput schema / title
      Removed value: -"dt_search_offersArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dt_search_offersDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.3/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 safety is covered. The description adds genuinely non-obvious behavior: pagination cuts an upstream page of ~40 items so `limit` should be raised to see the rest while `page` jumps a whole page, and it discloses the card payload (price, discounted price in Toman, pay_online as deposit vs pay-at-place, a default consultation_id).

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?

Front-loads purpose, then behavior, then next steps in four short lines with no wasted sentence. The telegraphic style ('No sort.', 'the rest at the place') is efficient but slightly terse, costing a point for minor ambiguity.

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 11 optional params, no output schema, and 100% schema coverage, the description supplies what structured fields cannot: pagination mechanics and the shape/meaning of returned cards. It omits any mention of the filter family (city, query, center, doctor, price bounds), which is acceptable since the schema documents each with examples, but a one-line hint would have completed the picture.

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?

Schema description coverage is 100%, so the baseline is 3. The description still goes beyond the schema by explaining the interaction between `limit` and the upstream `on_page` size and how `page` complements it, and by defining what the returned price/pay_online fields mean, which the schema does not.

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 and resource ('Search clinic offers') plus the concrete content (fixed-price procedures and packages: ultrasound, laser, dental, check-ups). It distinguishes itself from the detail sibling by naming dt_offer as the next step, so an agent can tell listing from single-offer retrieval without opening a 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?

The 'Next:' line explicitly routes to dt_offer, dt_free_slots, and dt_reviews(of='offer'), which is strong chaining guidance, and 'No sort' forecloses a plausible wrong assumption. It does not, however, contrast this tool with near-neighbors like dt_search_centers or dt_search_doctors for the case when the user thinks in terms of a place or a person rather than an offer.

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