Skip to main content
Glama
Sign In
paziresh24-mcp

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Hospital or clinic profile

pz_center
Read-onlyIdempotent

Get a hospital or clinic profile: type, address, phone, website, map, about, departments, and its doctors filtered by specialty.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
slugYesCenter slug from a pz_search_doctors center result (or its URL), e.g. 'بیمارستان-تخصصی-و-فوق-تخصصی-تریتا'.
full_textNoTrue = do not clip the about text (default 1500 chars).
specialtyNoOnly doctors whose department or specialty contains this Persian text, e.g. 'قلب'.
doctors_limitNoMax doctors to list (0 = none).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.0
    • removedInput schema / properties / doctors_limit / title
      Removed value: -"Doctors Limit"
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "True = do not clip the about text (default 1500 chars).",
+  "type": "boolean"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"Center slug from a pz_search_doctors center result (or its /center/... URL), e.g. 'بیمارستان-تخصصی-و-فوق-تخصصی-تریتا'."New value: +"Center slug from a pz_search_doctors center result (or its URL), e.g. 'بیمارستان-تخصصی-و-فوق-تخصصی-تریتا'."
    • removedInput schema / properties / slug / title
      Removed value: -"Slug"
    • changedInput schema / properties / specialty / description
      Previous value: -"Only doctors whose department or specialty contains this Persian text, e.g. 'قلب' or 'زنان'."New value: +"Only doctors whose department or specialty contains this Persian text, e.g. 'قلب'."
    • removedInput schema / properties / specialty / title
      Removed value: -"Specialty"
    • removedInput schema / title
      Removed value: -"pz_centerArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "pz_centerDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, openWorld), lowering the bar. The description adds genuine value by disclosing the return content (departments, per-doctor slug/department/specialty/insurances), which is the only place this is captured since there is no output schema. No auth or rate-limit notes, so not a 5.

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: the first defines the tool and its payload, the second gives the routing hint. Zero filler; every clause carries information.

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 must carry the return-shape burden, and it does list the returned fields. Combined with 100% parameter coverage and annotations handling the safety profile, an agent has enough to invoke it correctly; only the exact response structure is left implicit.

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%, so all four parameters (slug, full_text, specialty, doctors_limit) are already documented in the schema. The description itself adds no parameter-level syntax or semantics beyond the schema, so the baseline of 3 applies.

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?

The description states a specific resource (hospital/clinic profile) and enumerates exactly what it contains: type, address, phone, website, map, about, departments and doctors. This lets an agent distinguish it from pz_search_doctors (search) and pz_doctor (single doctor) without opening any schema.

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

Usage Guidelines4/5

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

It explicitly routes the agent onward ('Next: pz_search_doctors(center_id=..., sort='earliest') for its doctors by nearest free time, or pz_doctor'), and the schema's slug description names pz_search_doctors as the source. There is clear context but no explicit when-not-to-use or exclusion guidance.

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