Skip to main content
Glama

Suggest doctors, specialities and centers

dt_suggest
Read-onlyIdempotent

Returns search-box suggestions for Persian doctor names, specialty slugs, service tags, and centers so users can quickly pick a query and find doctors or clinics.

Instructions

Search-box suggestions: doctors (hash id), speciality slugs, service tags and centers for a free phrase.

Doctors match by name; for a speciality use its slug. Next: dt_search_doctors, dt_doctor, dt_center.

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": {
      "query": "<query>"
    },
    "name": "dt_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items of each kind.
queryYesPersian doctor name, speciality or symptom, e.g. 'قلب'.
city_idNoCity id from dt_cities to rank first, e.g. 2200.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.0
    • removedInput schema / properties / city_id / anyOf
      Removed value: -[
      -  {
      -    "maximum": 99999,
      -    "minimum": 1,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / city_id / description
      Previous value: -"Numeric city id from dt_cities to rank one city first, e.g. 2200 (Tehran)."New value: +"City id from dt_cities to rank first, e.g. 2200."
    • addedInput schema / properties / city_id / maximum
      Added value: +99999
    • addedInput schema / properties / city_id / minimum
      Added value: +1
    • addedInput schema / properties / city_id / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • changedInput schema / properties / query / description
      Previous value: -"What the user typed, in Persian: a doctor's name, a speciality or a symptom, e.g. 'قلب' or 'پرآذران'."New value: +"Persian doctor name, speciality or symptom, e.g. 'قلب'."
  2. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / city_id / title
      Removed value: -"City Id"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"dt_suggestArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dt_suggestDictOutput",
      -  "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 real behavioral value beyond that: doctors are matched by name and returned as hash ids, while specialities come back as slugs — the exact identifier shapes a caller needs for follow-up calls.

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 short lines with the result kinds front-loaded and follow-up tools last; nothing is wasted. The telegraphic 'Next:' fragment is efficient but slightly clipped for an agent parsing guidance.

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 small read-only autocomplete tool with no output schema, the description covers the result types and identifier formats a caller needs to act on the response. It leaves the exact response envelope (per-kind grouping, ordering) implicit, which is the only notable gap.

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 coverage is 100%, so all three parameters (including limit and city_id ranking) are already documented in the schema. The description adds matching semantics for the query ('doctors match by name; for a speciality use its slug'), which is useful but limited to one parameter, so it sits at the baseline-plus level.

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 set: 'Search-box suggestions' returning doctors (with hash id), speciality slugs, service tags and centers for a free phrase. The autocomplete framing plus the enumerated result kinds clearly separate it from the full search siblings (dt_search_doctors, dt_search_centers).

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 clear routing ('Next: dt_search_doctors, dt_doctor, dt_center') so the agent knows this is a discovery step that feeds into detail/search tools. It does not explicitly state when NOT to use it (e.g. when the user already has an exact doctor id), so it stops short of full when/when-not guidance.

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