Skip to main content
Glama
sepehr071

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Paziresh24 FAQ

pz_faq
Read-onlyIdempotent

Answer official Paziresh24 FAQ questions about booking, cancelling or moving appointments, online visits, payments and refunds. Omit a query to list available questions.

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.

Input Schema

NameRequiredDescriptionDefault
limitNoMax answers.
queryNoTopic words in Persian, e.g. 'لغو نوبت' (cancel), 'استرداد' (refund), 'ویزیت آنلاین' (online visit). Empty = list every question.
full_textNoTrue = do not clip answers (default 1500 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds real behavioral context beyond them by disclosing the no-query listing mode, but it never mentions that answers are clipped at 1500 characters by default, which materially affects what the agent receives.

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 the resource and its scope, followed by the one mode-switching behavior worth knowing. Every sentence earns its place with no redundancy.

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 FAQ retrieval tool with complete schema coverage and no output schema, the description covers domain, trigger condition and the no-query mode. The only notable omission is any hint that long answers are truncated unless full_text is set, which is left entirely to the schema.

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%, so limit, query and full_text are already fully documented in the schema (including Persian examples and the empty-list behavior). The description only restates the query-less listing mode, adding no new parameter semantics — the correct baseline of 3.

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?

Names a specific resource (the official Paziresh24 FAQ) and enumerates the content domains it covers: booking, cancelling/moving, online visits, payment and refunds. That is enough to separate it from the sibling data-lookup tools (pz_search_doctors, pz_visit_price, pz_holidays), 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?

"Use for 'how do I ...' questions about the site" gives a clear trigger condition, and "Without a query it lists the questions only" describes a distinct browse mode. There is no explicit when-not guidance or named alternative, but the usage context is unambiguous.

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