Skip to main content
Glama

Visit price

pz_visit_price
Read-onlyIdempotent

Get the exact Toman price of a doctor, clinic, or online-visit service, including fee, VAT, payable total, and cancel-refund policy; office visits typically return 0.

Instructions

Exact price of one service in Toman: fee, VAT and payable total (the online-visit invoice), plus the refund-on-cancel setting.

Office visits usually show 0.

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": {
      "center_id": "<center_id>",
      "user_center_id": "<user_center_id>",
      "service_id": "<service_id>"
    },
    "name": "pz_visit_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
center_idYescenter_id from pz_doctor or a search card; '5532' = online visit.
service_idYesservice_id at that center.
user_center_idYesuser_center_id of the same center.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • changedInput schema / properties / center_id / description
      Previous value: -"center_id from pz_doctor or a search card, e.g. '291c1bfe-e8f3-414a-a82d-d6fe081683fb'; '5532' = online visit."New value: +"center_id from pz_doctor or a search card; '5532' = online visit."
    • changedInput schema / properties / service_id / description
      Previous value: -"service_id of a service at that center."New value: +"service_id at that center."
    • changedInput schema / properties / user_center_id / description
      Previous value: -"user_center_id of the same center (doctor-at-center id)."New value: +"user_center_id of the same center."
  2. Changed8 schema fields changedv0.3.0
    • changedInput schema / properties / center_id / description
      Previous value: -"center_id from pz_doctor or a pz_search_doctors card, e.g. '291c1bfe-e8f3-414a-a82d-d6fe081683fb'; '5532' = online visit."New value: +"center_id from pz_doctor or a search card, e.g. '291c1bfe-e8f3-414a-a82d-d6fe081683fb'; '5532' = online visit."
    • removedInput schema / properties / center_id / title
      Removed value: -"Center Id"
    • changedInput schema / properties / service_id / description
      Previous value: -"service_id of a service at that center, e.g. '1a4a8ec2-fdf9-436e-a32b-8fc4485f609c'."New value: +"service_id of a service at that center."
    • removedInput schema / properties / service_id / title
      Removed value: -"Service Id"
    • changedInput schema / properties / user_center_id / description
      Previous value: -"user_center_id of the same center (the doctor-at-center id), e.g. '09558bad-168d-4df8-b39d-437a260ca6fc'."New value: +"user_center_id of the same center (doctor-at-center id)."
    • removedInput schema / properties / user_center_id / title
      Removed value: -"User Center Id"
    • removedInput schema / title
      Removed value: -"pz_visit_priceArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "pz_visit_priceDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive open-world operation. The description adds useful behavioral context by explaining the returned pricing components and the refund-on-cancel setting, plus the office-visit caveat that prices usually show 0.

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?

The description is two short sentences, front-loads the key output details, and the caveat about office visits is clearly separated. Every sentence adds useful information without unnecessary wording.

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 simple read-only pricing lookup with fully documented parameters and no output schema, the description is complete enough. It explains the returned price components, currency, refund setting, and the common zero-price case for office visits.

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 all three required parameters are already documented in the input schema. The description does not add meaning beyond the schema for center_id, service_id, or user_center_id, so the baseline score of 3 is appropriate.

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 states a specific resource and operation: the exact price of one service, broken into fee, VAT, payable total, and refund-on-cancel setting. It is clear about what is returned, but it does not explicitly distinguish this tool from sibling tools such as pz_center or pz_doctor.

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?

Usage is implied by the focus on one service and the note that office visits usually show 0, which helps set expectations. However, there is no explicit guidance on when to choose this tool over alternatives or what prerequisites are required beyond the schema.

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