Skip to main content
Glama

Specialities

dt_specialities
Read-onlyIdempotent

Retrieve medical specialty names and slugs to use when searching for doctors; optionally filter by query and see total matches.

Instructions

List specialities with the slug dt_search_doctors needs; total counts all matches.

parent is the broader speciality. Prefer query. Next: dt_search_doctors(speciality=slug).

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_specialities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries.
queryNoPart of name or slug, e.g. 'قلب'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max entries (about 100 exist)."New value: +"Max entries."
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 50,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / query / description
      Previous value: -"Part of the name or slug, e.g. 'قلب' or 'cardio'. Omit for all."New value: +"Part of name or slug, e.g. 'قلب'."
    • addedInput schema / properties / query / maxLength
      Added value: +50
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 150,
      +  "description": "Max entries (about 100 exist).",
      +  "maximum": 300,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Part of the name in Persian or the slug, e.g. 'قلب' or 'cardio'. Omit for all."New value: +"Part of the name or slug, e.g. 'قلب' or 'cardio'. Omit for all."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"dt_specialitiesArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dt_specialitiesDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its words elsewhere: it discloses that `total` counts all matches rather than the page returned, and that `parent` is the broader speciality. It does not mention the default page size or what happens when limit is hit, which would round out the read behavior.

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?

Roughly three short clauses, front-loaded with purpose, then result-field meaning, then next step. The telegraphic style ('List specialities with the slug X needs') is slightly awkward to parse but wastes no sentences.

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 it was important that the description explain the `total` and `parent` result fields, and it does. For a simple two-parameter lookup tool with full annotation coverage, nothing essential for correct invocation is missing.

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, but the description earns above baseline by advising which of the two parameters to use ('Prefer `query`') — a selection heuristic the schema cannot express. It says nothing extra about `limit`, which is fine since the schema fully documents it.

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 ('List specialities') and immediately ties the output to a consumer ('the slug dt_search_doctors needs'), which separates it from siblings like dt_cities or dt_insurances that also return lookup slugs.

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?

Gives an explicit param preference ('Prefer `query`') and an explicit next step ('Next: dt_search_doctors(speciality=slug)'), covering both how to call it and what to do with the result. The only minor gap is no guidance on when to skip `query` entirely.

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