Skip to main content
Glama

Neighborhoods

dt_neighborhoods
Read-onlyIdempotent

List neighborhoods and nearby cities for a given city with doctor counts, so you can choose an area before searching doctors by neighborhood.

Instructions

Neighborhoods of a city (most doctors first) and nearby cities, each with a doctor count.

Next: dt_search_doctors(city, neighborhood=slug).

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": {
      "city": "<city>"
    },
    "name": "dt_neighborhoods"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug from dt_cities, e.g. 'tehran'.
limitNoMax neighborhoods.
queryNoPart of Persian name or slug, e.g. 'پاسداران'.
specialityNoCount only this speciality, e.g. 'cardiologist'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.5.0
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 50,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / query / description
      Previous value: -"Part of the neighborhood name in Persian or slug, e.g. 'پاسداران'."New value: +"Part of Persian name or slug, e.g. 'پاسداران'."
    • addedInput schema / properties / query / maxLength
      Added value: +50
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • 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: -"Count only doctors of this speciality, e.g. 'cardiologist'."New value: +"Count only this speciality, 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"
      +]
  2. Changed6 schema fields changedv0.3.0
    • removedInput schema / properties / city / title
      Removed value: -"City"
    • 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_neighborhoodsArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dt_neighborhoodsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value beyond that by disclosing result ordering ('most doctors first') and the per-item doctor count. It says nothing about pagination, how nearby cities are ordered, or whether coverage is complete for cities with few doctors.

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?

Two short lines, front-loaded with what is returned and its ordering, followed by the single actionable next step. There is no filler and nothing that could be cut without losing information.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so adequately: neighborhoods, nearby cities, doctor counts and sort order. It leaves the exact response shape (fields, slug format) implicit, but the chaining hint compensates well enough for an agent to call it and use the result.

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 city, limit, query and speciality are all already documented in structured fields, which sets the baseline at 3. The description adds a little meaning by tying the returned neighborhood slug to the downstream 'neighborhood=slug' argument, but it does not clarify how query and speciality interact (e.g. whether query matches Persian names only).

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 resource (neighborhoods of a city plus nearby cities) and the returned attribute (doctor count, sorted most-doctors-first). It is clearly distinct from dt_cities and dt_search_centers, and the 'Next:' line separates it from dt_search_doctors. It stops short of 5 only because it never states the verb explicitly — an agent must infer that this is a listing/lookup call.

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: dt_search_doctors(city, neighborhood=slug)' line gives concrete follow-up guidance and shows exactly which argument shape the output feeds. It does not state when NOT to use this tool or when dt_cities or dt_specialities would be the better starting point, so it is clear context without exclusions.

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