Skip to main content
Glama
sepehr071

paziresh24-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Resolve a Paziresh24 URL

pz_resolve_url
Read-onlyIdempotent

Resolve a paziresh24.com link into its kind (doctor or center), slug, and clean URL. Use when a user pastes a link before calling pz_doctor or pz_center.

Instructions

Turn a paziresh24.com link into its kind ('doctor' or 'center'), slug and clean URL.

Use when the user pastes a link. Next: pz_doctor or pz_center.

Input Schema

NameRequiredDescriptionDefault
urlYespaziresh24.com link (/dr/..., /center/..., /factor/v2/...), e.g. 'https://www.paziresh24.com/dr/دکتر-هدیه-جباری-0/'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • changedInput schema / properties / url / description
      Previous value: -"A paziresh24.com link (doctor profile /dr/..., center /center/..., online visit /factor/v2/...), percent-encoded or not, e.g. 'https://www.paziresh24.com/dr/دکتر-هدیه-جباری-0/'."New value: +"paziresh24.com link (/dr/..., /center/..., /factor/v2/...), e.g. 'https://www.paziresh24.com/dr/دکتر-هدیه-جباری-0/'."
    • removedInput schema / properties / url / title
      Removed value: -"Url"
    • removedInput schema / title
      Removed value: -"pz_resolve_urlArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "pz_resolve_urlDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value by disclosing the returned content (kind, slug, clean URL), which is important since there is no output schema. Minor gap: no statement about failure behavior for unrecognized or non-paziresh24 URLs.

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, zero filler, with the input action front-loaded and the routing hint second. Nothing redundant with the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter URL parser with no output schema, the description covers the essential facts: input source (pasted link), encoded result fields, and the follow-up tools. An agent has everything needed to call it correctly.

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 single 'url' parameter is fully documented in-schema with length bounds and example path formats. The description adds nothing about parameter syntax beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('turn a paziresh24.com link into...') and enumerates the outputs: kind ('doctor' or 'center'), slug, clean URL. This clearly differentiates it from the sibling search/lookup tools, which take queries rather than URLs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when the user pastes a link' gives an explicit trigger condition, and 'Next: pz_doctor or pz_center' names the downstream alternatives an agent should route to based on the returned kind. The agent knows both when to call it and what to do afterwards.

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