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 available appointment days for a specific service at one center across the full booking window, while accounting for weekly days off and holidays.

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.

Next: pz_free_slots for times.

Input Schema

NameRequiredDescriptionDefault
center_idYescenter_id from pz_doctor or a search card; '5532' = online visit.
service_idYesservice_id at that center.
user_center_idYesuser_center_id of the same center.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / 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. 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
  3. 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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds domain context the annotations cannot: the window is often 6-8 weeks and weekly days off and holidays are excluded, which sets expectations about gaps in results. It does not say how the days are ordered or returned, which is the remaining gap.

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 with zero waste: the scope and window constraints are front-loaded, and the hand-off to the sibling follows immediately. Every phrase carries information an agent needs.

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 read-only lookup with fully documented parameters and annotations covering the safety profile, the description supplies the window size, the exclusion of days off and holidays, and the next step. The only omission is what the output looks like — a list of dates — which there is no output schema to cover.

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% and each parameter already carries its own description, including the special '5532' online-visit case. The description adds nothing about parameter meaning beyond what the schema documents, so the baseline 3 applies.

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 for one service at one center — and scopes it to the whole booking window. It clearly separates itself from pz_free_slots, which handles times rather than days, so an agent can pick between them. It stops short of an explicit verb like 'list', which keeps it from a 5.

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?

The closing 'Next: pz_free_slots for times' gives a concrete routing rule to the sibling tool once a day is chosen, which is the main branching decision here. There is no explicit statement of when not to use it, e.g. for a different center or a direct slot lookup, so it falls short of full when/when-not coverage.

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