Skip to main content
Glama
Sign In
paziresh24-mcp

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Free appointment days

pz_free_days
Read-onlyIdempotent

Find days with free appointments for a selected service at a center across the full booking window, excluding weekly days off and holidays. Then check times for chosen days.

Instructions

Days with a free appointment for one service at one center over the whole booking window (often 6-8 weeks), with weekly days off and holidays.

Ids from pz_doctor. Next: pz_free_slots for the times of chosen days.

Input Schema

NameRequiredDescriptionDefault
center_idYescenter_id from pz_doctor or a search card, e.g. '291c1bfe-e8f3-414a-a82d-d6fe081683fb'; '5532' = online visit.
service_idYesservice_id of a service at that center.
user_center_idYesuser_center_id of the same center (doctor-at-center id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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 / 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_daysArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "pz_free_daysDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, open-world read, so the bar is lower. The description adds genuine behavioral context beyond that: the booking window span (often 6-8 weeks) and that weekly days off and holidays are factored in, which explains why some days are absent from results.

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 tight sentences with zero waste: purpose and scope first, then the workflow pointer. Front-loaded and easy to scan.

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 annotations covering the safety profile, all three params documented in the schema, and no output schema required, the description supplies the needed purpose and continuation. Minor gap: no hint about result shape or volume for a window that can span weeks.

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 the schema already states where each id comes from (pz_doctor, search card). The description's 'Ids from pz_doctor' largely repeats the schema rather than adding new meaning, so baseline 3 is appropriate.

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 resource (days with a free appointment) scoped to one service at one center across the entire booking window, and names pz_free_slots as the follow-on. It clearly separates itself from pz_free_slots, though it leaves the distinction from pz_first_available unstated.

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?

Provides a workflow chain: ids come from pz_doctor, and pz_free_slots should be called next to get times for chosen days. This gives clear context for when to invoke it, but no explicit when-not/tie-breaking guidance against other availability siblings.

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