Skip to main content
Glama

Earliest free appointment

pz_first_available
Read-onlyIdempotent

Check whether a doctor is bookable now and find the nearest free appointment slot by center, in person or online, using the doctor slug or profile URL (Tehran time).

Instructions

Whether a doctor can be booked now and the nearest free slot, in person, online and per center (Tehran time).

Quick check; names and service ids are in pz_doctor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "pz_first_available"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / slug / description
      Previous value: -"Doctor slug (Persian, e.g. 'دکتر-هدیه-جباری-0') or profile URL."New value: +"Doctor slug (Persian, e.g. 'دکتر-هدیه-جباری-0') or URL."
  2. 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
  3. First observedv0.1.0

TDQS

A3.7/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 bar is lower. The description still adds real context: results are in Tehran time and broken out by in-person, online and per-center availability, and doctor identifiers must come from pz_doctor. It does not describe the response shape, which matters since no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero padding, with the core capability front-loaded. The second sentence is telegraphic ('Quick check; names and service ids are in pz_doctor') and 'per center' is left under-explained.

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 one-parameter read-only tool with no output schema, the description gives enough to call it correctly and to anticipate the return content (bookability, nearest slot, channel breakdown, timezone). A brief note on what an unavailable doctor returns would close the remaining gap.

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% with a single well-documented slug parameter, so the schema does the work. The description contributes no extra meaning about the slug beyond noting that names and service ids live in pz_doctor.

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?

The description names a specific outcome (whether a doctor can be booked now plus the nearest free slot) and scopes it across in-person, online and per-center views in Tehran time. It implicitly separates itself from pz_free_slots/pz_free_days via the 'Quick check' framing, but never names those siblings explicitly.

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?

'Quick check' implies this is the lightweight summary to reach for when a yes/no plus nearest slot suffices, and it points to pz_doctor for names and service ids. However, it never states when to prefer pz_free_slots or pz_free_days instead, so the routing decision is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.