Skip to main content
Glama
sepehr071

doctoreto-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Cities

dt_cities
Read-onlyIdempotent

Find a city's slug for search filters and numeric ID for dt_suggest, with optional speciality counts. Use the slug for dt_search_doctors or dt_neighborhoods.

Instructions

Find a city's slug (for search filters) and numeric id (for dt_suggest); main cities first.

With speciality: only main cities that have such doctors, with counts (a search may find more elsewhere). Next: dt_search_doctors(city=slug) or dt_neighborhoods.

Input Schema

NameRequiredDescriptionDefault
limitNoMax cities.
queryNoPart of the city name in Persian or the slug, e.g. 'شیراز'.
specialityNoOnly cities that have doctors of this speciality, with counts, e.g. 'cardiologist'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / speciality / title
      Removed value: -"Speciality"
    • removedInput schema / title
      Removed value: -"dt_citiesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dt_citiesDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.7/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 the safety profile is covered. The description adds behavior beyond that: result ordering (main cities first) and the caveat that the speciality-filtered list is limited to main cities with counts and may understate what a full search returns. It doesn't discuss pagination explicit behavior, but the value-add is real.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short lines: purpose and ordering first, conditional speciality behavior second, next-step routing third. No filler sentences; every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey what comes back — and it does: slug, numeric id, ordering, and count-augmented results under speciality. Combined with the fully-described parameters, an agent has everything needed to call and consume this tool.

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 coverage is 100%, so the baseline is 3. The description goes further by explaining the purpose of the returned slug and id and by clarifying that speciality restricts to main cities and adds counts — semantics not present in the schema's one-line parameter descriptions.

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: it finds a city's slug (for search filters) and numeric id (for dt_suggest), and explicitly notes main cities come first. It names the two downstream tools the outputs feed, so an agent can distinguish it from dt_suggest and dt_search_doctors without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit routing: 'Next: dt_search_doctors(city=slug) or dt_neighborhoods', plus a documented conditional branch explaining what the speciality filter changes and warning that a broader search may find more elsewhere. When-to-use and what-to-do-next are both spelled out.

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