Skip to main content
Glama

Resolve a Paziresh24 URL

pz_resolve_url
Read-onlyIdempotent

Parses a pasted paziresh24.com URL to identify whether it is a doctor or center, extract its slug, and return a clean link for reliable profile handling.

Instructions

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

Use when the user pastes a link.

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": {
      "url": "<url>"
    },
    "name": "pz_resolve_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespaziresh24.com link (/dr/..., /center/..., /factor/v2/...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / url / description
      Previous value: -"paziresh24.com link (/dr/..., /center/..., /factor/v2/...), e.g. 'https://www.paziresh24.com/dr/دکتر-هدیه-جباری-0/'."New value: +"paziresh24.com link (/dr/..., /center/..., /factor/v2/...)."
  2. 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
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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 usefully reveals the return payload (kind, slug, clean URL) in the absence of an output schema, but it says nothing about invalid/unsupported links or about the /factor/v2/ prefix the schema advertises, which does not map to either the 'doctor' or 'center' kind.

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 lines: the capability first, the trigger second. Every sentence earns its place and there is no filler or redundant restatement of the tool name.

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 rich annotations and no output schema, the description covers both what goes in and what comes out. The remaining gap is edge-case behavior for malformed or unsupported link types, which an agent would need to handle gracefully.

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?

There is a single parameter with 100% schema description coverage, so the schema already carries the semantics, including the accepted path prefixes and length bounds. The description only restates 'paziresh24.com link' and adds no format or parsing detail beyond it, matching the baseline for full schema coverage.

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 gives a specific transformation verb ('Turn ... into') and enumerates the outputs (kind, slug, clean URL), which makes it clearly distinct from the entity-fetching siblings like pz_doctor or pz_center. It stops short of explicitly contrasting itself with those siblings, so it lands just under 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?

'Use when the user pastes a link' gives an actionable trigger condition that an agent can pattern-match on. There is no guidance on when not to use it or which sibling to pick if the link is a search-style URL, but the primary context is clear.

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