Skip to main content
Glama

Paziresh24 FAQ

pz_faq
Read-onlyIdempotent

Answers "how do I..." questions about Paziresh24 using the official FAQ, covering booking, cancelling or moving visits, online consultations, payments and refunds. Lists all questions when no query is given.

Instructions

Answers from the official Paziresh24 FAQ: booking, cancelling or moving, online visits, payment and refunds.

Without a query it lists the questions only. Use for "how do I ..." questions about the site.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pz_faq"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoPersian topic words, e.g. 'لغو نوبت'. Empty = list every question.
full_textNoDo not clip answers (1500 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • changedInput schema / properties / full_text / description
      Previous value: -"True = do not clip answers (default 1500 chars)."New value: +"Do not clip answers (1500 chars)."
    • removedInput schema / properties / limit / description
      Removed value: -"Max answers."
    • changedInput schema / properties / query / description
      Previous value: -"Topic words in Persian, e.g. 'لغو نوبت' (cancel), 'استرداد' (refund), 'ویزیت آنلاین' (online visit). Empty = list every question."New value: +"Persian topic words, e.g. 'لغو نوبت'. Empty = list every question."
  2. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
      +  "default": false,
      +  "description": "True = do not clip answers (default 1500 chars).",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"pz_faqArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "pz_faqDictOutput",
      -  "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 establish this as a read-only, idempotent, non-destructive lookup, so the safety burden is light. The description adds behavior the annotations do not: the no-query fallback returns only the list of questions rather than answers. It does not say whether answers are quoted verbatim from the FAQ or synthesized, which would have been the final piece.

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 sentences, zero filler, with the resource and topic coverage front-loaded and the fallback behavior plus usage cue following. Every clause 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 three-optional-parameter FAQ lookup with no output schema, the description covers purpose, domain, usage cue and the empty-query behavior. The one remaining gap is the return shape of an answered query (single answer vs. list of matched entries), which is not covered by an output schema either.

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 67%: query and full_text are documented in the schema, while limit has only default/min/max bounds. The description contributes the key semantic that an omitted query degrades the tool to a question listing, which is genuinely useful beyond the schema. However, it adds nothing about limit or result ordering.

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 verb and resource ('Answers from the official Paziresh24 FAQ') and enumerates the covered topic domains: booking, cancelling/moving, online visits, payment and refunds. That scope makes it obviously distinct from the sibling tools (doctors, centers, slots, prices, reviews), though no sibling is named explicitly.

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?

It gives a concrete selection cue: 'Use for "how do I ..." questions about the site.' That is a clear when-to-use signal tied to an intent pattern. It does not state when not to use it or which sibling to prefer for adjacent needs (e.g. price questions vs pz_visit_price).

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