Podyx MCP

podyx_quote_tour

Read-onlyIdempotent

Preview advisory Tour pricing for validated selected addons based on current price, addon versions, quantities, and duration; it does not reserve slots or lock prices.

Instructions

Read advisory Tour pricing for strictly validated selected addons POST /api/v2/studio-tours/{id}/quotes. Advisory selection pricing using the Tour's current price, current addon versions, quantities and duration. Malformed or unavailable selected addons are refused. This read creates no Client, booking, hold, payment, receipt or job and makes no completeness or charge-ready assertion. Read the Tour offer for required details and consents and availability for scheduling choices; checkout still validates every current requirement. Requires sessions:read, current key/account/public_api authority and studio_tour entitlement. Pricing reads remain available when headless new entry is disabled. No Idempotency-Key is required. Read/preview only. Follow all pagination; a quote does not reserve a slot or lock a price.

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": {
      "path": "<path>",
      "body": "<body>"
    },
    "name": "podyx_quote_tour"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes
`path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 7, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the important behaviors: no Client, booking, hold, payment, receipt or job is created, no completeness or charge-ready claim is made, no Idempotency-Key is needed, scope and entitlement requirements are listed, and pricing reads still work when headless new entry is disabled. It also warns that a quote reserves no slot and locks no price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a dense run-on that mixes raw HTTP endpoint text with several overlapping non-mutation disclaimers ('creates no Client, booking, hold...' then 'does not reserve a slot or lock a price'; 'Read/preview only' plus 'Pricing reads remain available...'). The 'Follow all pagination' line is boilerplate with no obvious relevance to a quote endpoint.

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

Completeness3/5

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

Auth, entitlement and non-mutation semantics are well covered, but there is no output schema and the description says nothing about what a quote actually returns (price breakdowns, currency, per-addon lines), which is the core value of a quote call. Combined with zero parameter documentation, the agent knows the guardrails but not the shape of the result.

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 0%, so the description must carry the load; it mentions selected addons, quantities and duration-based pricing, which maps loosely to the body's addons[].addon_id/quantity. It never explains the path id as the Tour identifier, that the body accepts only an addons array, or the UUID/minimum-quantity constraints, so an agent still has to infer structure from the schema alone.

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?

States a specific verb and resource ('Read advisory Tour pricing for ... selected addons') plus the underlying endpoint, and clarifies it prices addon selections against the Tour's current price and addon versions. It is distinguishable from the broader booking/checkout quote siblings, but it never names those siblings explicitly, so the boundary is inferred rather than stated.

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?

Gives clear usage context: this is a pre-checkout pricing read, and for required details/consents/availability the agent is pointed at the Tour offer and availability tools, with checkout still validating every requirement. It does not explicitly name the alternative quote tools (e.g. booking/bundle quotes) or say when not to use this one.

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

Deploy Server