Skip to main content
Glama
Sign In
paziresh24-mcp

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Free appointment slots

pz_free_slots
Read-onlyIdempotent

Finds free appointment start times (Tehran HH:MM) for one service at a center across a date range and returns the next available day when none exist.

Instructions

Free appointment start times (Tehran HH:MM) per day for one service at one center, for a date range.

With no free slot in the range, next_free_day gives the next one.

Input Schema

NameRequiredDescriptionDefault
date_toNoInclusive, default date_from; max 14 days after it.
center_idYescenter_id from pz_doctor or a search card; '5532' = online visit.
date_fromNoGregorian YYYY-MM-DD, default today.
service_idYesservice_id at that center.
user_center_idYesuser_center_id of the same center.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • changedInput schema / properties / center_id / description
      Previous value: -"center_id from pz_doctor or a search card, e.g. '291c1bfe-e8f3-414a-a82d-d6fe081683fb'; '5532' = online visit."New value: +"center_id from pz_doctor or a search card; '5532' = online visit."
    • changedInput schema / properties / date_from / description
      Previous value: -"First day, Gregorian YYYY-MM-DD (default today), e.g. '2026-10-10'."New value: +"Gregorian YYYY-MM-DD, default today."
    • changedInput schema / properties / date_to / description
      Previous value: -"Last day, inclusive (default date_from); at most 14 days after it."New value: +"Inclusive, default date_from; max 14 days after it."
    • changedInput schema / properties / service_id / description
      Previous value: -"service_id of a service at that center."New value: +"service_id at that center."
    • changedInput schema / properties / user_center_id / description
      Previous value: -"user_center_id of the same center (doctor-at-center id)."New value: +"user_center_id of the same center."
  2. Changed12 schema fields changedv0.3.0
    • changedInput schema / properties / center_id / description
      Previous value: -"center_id from pz_doctor or a pz_search_doctors card, e.g. '291c1bfe-e8f3-414a-a82d-d6fe081683fb'; '5532' = online visit."New value: +"center_id from pz_doctor or a search card, e.g. '291c1bfe-e8f3-414a-a82d-d6fe081683fb'; '5532' = online visit."
    • removedInput schema / properties / center_id / title
      Removed value: -"Center Id"
    • changedInput schema / properties / date_from / description
      Previous value: -"First day, Gregorian YYYY-MM-DD (default today in Iran), e.g. '2026-10-10'."New value: +"First day, Gregorian YYYY-MM-DD (default today), e.g. '2026-10-10'."
    • removedInput schema / properties / date_from / title
      Removed value: -"Date From"
    • changedInput schema / properties / date_to / description
      Previous value: -"Last day, inclusive (default date_from); at most 14 days after date_from."New value: +"Last day, inclusive (default date_from); at most 14 days after it."
    • removedInput schema / properties / date_to / title
      Removed value: -"Date To"
    • changedInput schema / properties / service_id / description
      Previous value: -"service_id of a service at that center, e.g. '1a4a8ec2-fdf9-436e-a32b-8fc4485f609c'."New value: +"service_id of a service at that center."
    • removedInput schema / properties / service_id / title
      Removed value: -"Service Id"
    • changedInput schema / properties / user_center_id / description
      Previous value: -"user_center_id of the same center (the doctor-at-center id), e.g. '09558bad-168d-4df8-b39d-437a260ca6fc'."New value: +"user_center_id of the same center (doctor-at-center id)."
    • removedInput schema / properties / user_center_id / title
      Removed value: -"User Center Id"
    • removedInput schema / title
      Removed value: -"pz_free_slotsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "pz_free_slotsDictOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it read-only, idempotent, non-destructive, and open-world. Beyond that, the description discloses the return shape (start times in Tehran HH:MM grouped per day) and the graceful-empty behavior pointing to `next_free_day`, which is real behavioral context the annotations do not provide.

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 what is returned and its granularity, then the edge-case fallback. Nothing is redundant or 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?

With no output schema, the description supplies the essential return contract (per-day start times, Tehran time) and the empty-result behavior. It does not mention error cases such as a service not offered at the given center, but for a read-only lookup of this size it is largely sufficient.

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%, including the same-center constraint, the 14-day span limit, and the '5532' online-visit convention, so the schema already carries parameter meaning. The description only reinforces the one-service/one-center framing and specifies the output timezone, which is a modest addition over baseline.

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?

States a specific verb and resource: free appointment start times, scoped to one service at one center over a date range. The scope qualifiers let an agent distinguish it from a broad availability search, though it never names its closest sibling pz_free_days to contrast day-level vs slot-level results.

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?

Usage is implied by the scoping (one service, one center, date range) and the description adds a useful fallback path via the `next_free_day` field when the range is empty. It does not explicitly say when to prefer pz_free_days or pz_first_available instead, so the agent must infer the choice.

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