Skip to main content
Glama
sepehr071

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Earliest free appointment

pz_first_available
Read-onlyIdempotent

Check if a doctor can be booked now and find the nearest free appointment slot for in-person or online visits at each center in Tehran time.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
slugYesDoctor slug (Persian, e.g. 'دکتر-هدیه-جباری-0') or profile URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • 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_first_availableArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "pz_first_availableDictOutput",
-  "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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely new context: that it answers a yes/no bookability question, returns the nearest slot, and expresses results in Tehran time.

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 short sentences, front-loaded with the core answer (can this doctor be booked now), followed by scope and the sibling routing hint. 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?

For a single-param, no-output-schema read tool with rich annotations, the description covers what comes back and when to reach for it. The phrase "per center" is mildly ambiguous given the tool accepts only a doctor slug.

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?

Only one parameter and schema coverage is 100%, with the schema already documenting the slug format (Persian slug or profile URL). The description adds nothing about the slug, 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?

States a specific verb+resource: reports whether a doctor is bookable now plus the nearest free slot, and scopes it to in-person, online and per-center with an explicit time zone. It also positions itself against siblings (pz_free_days / pz_free_slots), so an agent can tell it apart without opening another 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?

"A quick check before pz_free_days / pz_free_slots" gives explicit ordering guidance and names the alternative tools it precedes. It stops short of stating when NOT to use it (e.g. when you already know the date window and should go straight to free_slots).

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