Podyx MCP

podyx_booking_quote

Read-onlyIdempotent

Preview booking selections and checkout requirements, returning missing inputs, forms, consent documents, and file-transfer choices without creating bookings or locking prices.

Instructions

Preview current customer booking selections and checkout requirements POST /api/v2/bookings/quotes. Read-only POST: incomplete selections return status=incomplete and missing_inputs, with current CMS-configured forms, guest limit, recording seats, invoice fields, rail-specific displayed consent documents and paginated file-transfer choices. No client, booking, hold, payment or receipt is created. Prices, tax, promo eligibility and credits are resolved by Podyx; amounts or provider IDs in input are refused. A fingerprint identifies advisory facts, never a price lock or permission to charge. Complete means required selections, details, invoice fields and consent acceptance are supplied; later commands must revalidate. client_id means a currently owned studio Client, requires clients:read in addition to the family read permission, and is never visitor login. Omit it for anonymous preview; email is not accepted here. Existing public_api/account/current-key authority remains required, including after reads. Disabling headless new entry preserves authorized quote reads. Booking sessions are explicit and multi-session; Studio Tour has its own published quote and booking operations. Subscription quotes additionally accept payment_source=native|external, default native: external previews studio collection independently of native provider cadence restrictions; actual studio approval still applies and no collection is reported. Other quote families do not accept payment_source. Bundle/subscription never ask for refund policy; tour consent remains terms only. page/per_page page file-transfer choices only, using the existing 1..100 bounds. 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": {
      "body": "<body>"
    },
    "name": "podyx_booking_quote"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 7, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description adds substantial context beyond them: 'No client, booking, hold, payment or receipt is created', that amounts or provider IDs in input are refused, that the fingerprint is 'never a price lock or permission to charge', that later commands must revalidate, and that reads require clients:read plus family read permission. This is exactly the behavioral disclosure an agent needs for a read-only POST that is easy to mistake for a commitment.

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?

Purpose is correctly front-loaded, but the remainder is a dense, run-on block mixing this tool's constraints with other quote families' rules (subscription payment_source, bundle refund policy), which adds reading cost. Little of it is wasted factually, but structure and scannability suffer.

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 complex preview with no output schema, it covers the important return semantics (status=incomplete, missing_inputs, CMS forms, guest limit, recording seats, consent documents, paginated file-transfer choices) and the no-side-effect guarantee. Remaining gap is request-field meaning for the nested body.

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% and the body is a deep nested object, so the description must carry the load. It does well for client_id (owned studio Client vs visitor login, permission implications) and page/per_page bounds, but leaves promo_code, credit_choice, invoice_profile.billing_fields, consents semantics, and most session fields uninterpreted. Partial compensation, not full.

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?

Opens with a specific verb+resource ('Preview current customer booking selections and checkout requirements'), plus the endpoint. It also differentiates from sibling quote families: 'Other quote families do not accept payment_source' and 'Studio Tour has its own published quote and booking operations', so an agent can separate this from subscription/bundle/tour quotes.

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 concrete routing rules: 'Omit it for anonymous preview; email is not accepted here', and points tour quoting to its own operations. It also instructs 'Follow all pagination'. It stops short of a systematic when-to-use/when-not matrix across the four sibling quote tools, but the exclusions it does state are actionable.

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

Deploy Server