Skip to main content
Glama
sepehr071

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Suggest cities, specialties and queries

pz_suggest
Read-onlyIdempotent

Convert a city, specialty, symptom, or doctor-name query into Paziresh24 search arguments, returning matching cities, specialties with slugs, and query completions for doctor searches.

Instructions

Turn words into pz_search_doctors arguments: matching cities, specialties (with slugs) and the site's query completions (use one as text).

Call first when you lack the city or specialty slug. Next: pz_search_doctors.

Input Schema

NameRequiredDescriptionDefault
limitNoMax items in each list.
queryYesCity ('تهران', 'shiraz'), specialty or symptom ('قلب'), or start of a doctor's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • changedInput schema / properties / query / description
      Previous value: -"Persian or English word: a city ('تهران', 'shiraz'), a specialty or symptom ('قلب', 'پوست'), or the start of a doctor's name."New value: +"City ('تهران', 'shiraz'), specialty or symptom ('قلب'), or start of a doctor's name."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"pz_suggestArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "pz_suggestDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so safety is covered. The description adds real behavioral context beyond them: it is a slug-resolution step, it returns slug-bearing lists, and one completion should be reused as a downstream `text` value.

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 sentences, front-loaded with the transformation and followed by the ordering instruction. No filler.

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 no output schema, the description responsibly sketches the return shape (cities, specialties with slugs, completions). Minor ambiguity remains: it references a `text` argument that belongs to pz_search_doctors rather than this tool, which could momentarily confuse an agent.

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% and both params are documented (the `query` description even enumerates city/specialty/name forms), so the schema does the heavy lifting. The description only adds that outputs become arguments for another tool, not new meaning for `query` or `limit`.

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 concrete transformation ('turn words into pz_search_doctors arguments') and enumerates exactly what comes back: cities, specialties with slugs, and query completions. This clearly distinguishes it from the sibling pz_search_doctors it feeds.

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 trigger ('Call first when you lack the city or specialty slug') and the follow-up step ('Next: pz_search_doctors'). The agent knows both when to use it and where to go afterwards.

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