Skip to main content
Glama
Sign In
paziresh24-mcp

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Doctor profile

pz_doctor
Read-onlyIdempotent

Retrieve a doctor’s full profile—specialties, ratings, insurances, visit prices, centers, services, and first free appointment slots—to compare options and book via the provided link.

Instructions

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).

booking_off: true = booking switched off (call the phone); booking_opens = new slots open then. A service's center_id + user_center_id + service_id feed the slot and price tools.

Input Schema

NameRequiredDescriptionDefault
slugYesDoctor slug (Persian, e.g. 'دکتر-هدیه-جباری-0') or URL.
full_textNoDo not clip about (1200 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / full_text / description
      Previous value: -"True = do not clip the about text (default 1200 chars)."New value: +"Do not clip about (1200 chars)."
    • changedInput schema / properties / slug / description
      Previous value: -"Doctor slug (Persian, e.g. 'دکتر-هدیه-جباری-0') or profile URL."New value: +"Doctor slug (Persian, e.g. 'دکتر-هدیه-جباری-0') or URL."
  2. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "True = do not clip the about text (default 1200 chars).",
+  "type": "boolean"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"Doctor slug from pz_search_doctors (Persian, e.g. 'دکتر-هدیه-جباری-0') or the doctor's paziresh24.com profile URL."New value: +"Doctor slug (Persian, e.g. 'دکتر-هدیه-جباری-0') or profile URL."
    • removedInput schema / properties / slug / title
      Removed value: -"Slug"
    • removedInput schema / title
      Removed value: -"pz_doctorArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "pz_doctorDictOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.0

TDQS

A3.7/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 safety is covered. The description adds real behavioral context beyond them: the semantics of booking_off (call the phone) and booking_opens (new slots open then), the about-field clipping at 1200 chars, and the cross-tool key handoff. That is meaningful domain behavior the agent could not get from annotations alone.

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?

Front-loaded with the core payload list, then two compact operational notes in backticks. Dense but every clause carries information; the backtick shorthand is terse yet readable. Minor telegraphic style ('booking_opens = new slots open then') costs a point but nothing is padded.

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 bears the burden of describing returns, and it does so by enumerating every profile section and per-center service fields. With annotations covering safety and only two simple parameters, an agent has what it needs to call it and interpret booking state; only explicit sibling disambiguation is missing.

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% and both parameters (slug with Persian example/URL, full_text clipping) are already documented in the schema. The description only echoes the clipping behavior in passing and adds no new parameter-level meaning, so baseline 3 applies.

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 first sentence names a specific resource (one doctor's full profile) and enumerates the returned payload: specialties, about, ratings, insurances, online visit channels/price, and every center with address, phone, map, first free slot and services. That is far more specific than a title restatement. It stops short of explicitly naming which sibling to prefer (e.g. pz_reviews for reviews only), so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Use is implied (you need a doctor's slug to get the full picture) and there is a useful downstream instruction that a service's center_id + user_center_id + service_id feed the slot and price tools. However, there is no explicit 'use this instead of pz_reviews / pz_center / pz_search_doctors when...' guidance, leaving the agent to infer sibling boundaries from names.

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