Skip to main content
Glama
Sign In
paziresh24-mcp

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Doctor reviews

pz_reviews
Read-onlyIdempotent

Fetch paged patient reviews for a doctor by slug or profile URL, including star ratings, verified visit details, and first-page rating/wait-time summaries; reviewer identities are excluded.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
slugYesDoctor slug (Persian, e.g. 'دکتر-هدیه-جباری-0') or profile URL.
sortNo'relevant' = the site's default order.relevant
limitNoReviews per page.
offsetNoReviews to skip, e.g. 5 for page 2.
full_textNoTrue = do not clip review text (default 400 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "True = do not clip review text (default 400 chars).",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / default
      Previous value: -10New value: +5
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • changedInput schema / properties / offset / description
      Previous value: -"Reviews to skip (paging), e.g. 10 for page 2."New value: +"Reviews to skip, e.g. 5 for page 2."
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • 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"
    • changedInput schema / properties / sort / description
      Previous value: -"'relevant' = the site's default order, 'newest' first."New value: +"'relevant' = the site's default order."
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"pz_reviewsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "pz_reviewsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the 400-character clip on review text, that the summary appears only on the first page, and the privacy guarantee that reviewer names and ids are never returned.

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?

Two sentences, tightly front-loaded on the payload contents, with the privacy note last. The parenthetical list is dense but every item is load-bearing; nothing is redundant.

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 carries the burden of describing the return shape, and it does so field-by-field including the first-page-only summary. Minor gap: it does not say how many total reviews exist or how to detect the last page, which matters for a paged tool.

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%, so sort/limit/offset/full_text semantics are already documented in the schema and the 3 baseline applies. The description reinforces the clip behavior tied to full_text but adds no syntax, ranges or pagination math beyond what the schema states.

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 states precisely what is returned: patient reviews with stars, clipped text, visit reason, center and verified-visit flag, plus a first-page summary of averages, counts and waiting times. It is clearly distinguishable from the doctor/center/search siblings by resource (reviews), though it never names them for contrast.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives among the twelve sibling tools. The reader must infer from the 'slug' parameter that this is invoked on a doctor profile; nothing in the description says so.

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