paziresh24-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAZIRESH24_MCP_PROXY | No | HTTP proxy for every request, e.g. http://user:pass@host:port |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pz_suggestA | Turn words into pz_search_doctors arguments: matching cities, specialties (with slugs) and the site's query completions (use one as Call first when you lack the city or specialty slug. Next: pz_search_doctors. |
| pz_search_doctorsA | Search doctors (or hospitals and clinics) by city, specialty, name, visit type, gender and degree, sorted and paged. Doctor cards carry slug, |
| pz_resolve_urlA | Turn a paziresh24.com link into its kind ('doctor' or 'center'), slug and clean URL. Use when the user pastes a link. Next: pz_doctor or pz_center. |
| pz_centerA | Profile of a hospital or clinic: type, address, phone, website, map, about, departments and its doctors (slug, department, specialty, basic insurances). Next: pz_search_doctors(center_id=..., sort='earliest') for its doctors by nearest free time, or pz_doctor. |
| pz_doctorA | Full profile of one doctor: specialties, about, rating averages, insurances, online visit (channels, price in Toman) and every center with address, phone, map, first free slot and services (ids, price, duration, hours).
|
| pz_first_availableA | Whether a doctor can be booked now and the nearest free slot, in person, online and per center (Tehran time). A quick check before pz_free_days / pz_free_slots; names and service ids are in pz_doctor. |
| pz_reviewsA | Patient reviews (stars 1-5, text clipped to 400 chars, visit reason, center, verified visit), paged, plus on the first page a summary: rating averages, counts and waiting time per center. Reviewer names and ids are never returned. |
| pz_faqA | Answers from the official Paziresh24 FAQ: booking, cancelling or moving, online visits, payment and refunds. Without a query it lists the questions only. Use for "how do I ..." questions about the site. |
| pz_free_daysA | Days with a free appointment for one service at one center over the whole booking window (often 6-8 weeks), with weekly days off and holidays. Ids from pz_doctor. Next: pz_free_slots for the times of chosen days. |
| pz_free_slotsA | Free appointment start times (Tehran HH:MM) per day for one service at one center, for a date range. Ids from pz_doctor or a search card; find days with pz_free_days. With no free slot in the range,
|
| pz_visit_priceA | Exact price of one service in Toman: fee, VAT and payable total (the online-visit invoice), plus the refund-on-cancel setting. Most useful for online visits (center_id '5532'); office visits usually show 0. |
| pz_holidaysA | Official Iranian public holidays and occasions between two dates (Persian name, Hijri date). Fridays are not listed. Use before suggesting appointment days. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct step in the booking research workflow: URL parsing, search suggestions, search, profiles, availability checks, reviews, FAQ, holidays, and pricing. Tool descriptions explicitly clarify boundaries and next steps, leaving almost no room for misselection.
All tools use a consistent 'pz_' prefix and snake_case, with clear, descriptive names. The only deviation from a strict verb_noun pattern is that several tools are noun-only (e.g., pz_center, pz_doctor, pz_reviews), but this remains predictable and readable.
Twelve tools are well-scoped for a medical appointment discovery domain, with each tool earning its place (search, profiles, availability, pricing, reviews, FAQ, holidays, and URL resolution). No tool feels redundant or excessive.
The surface thoroughly covers discovery, availability, and pricing, with clear guidance for each step. However, no tool enables actual booking, cancellation, or user account actions, which are notable gaps for a booking platform, though the server may intentionally be read-only.