Podyx MCP

podyx_bundle_quote

Read-onlyIdempotent

Preview bundle purchase quotes and checkout requirements without creating bookings, holds, or payments; incomplete selections return missing inputs for correction.

Instructions

Preview current customer bundle selections and checkout requirements POST /api/v2/bundle-purchases/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_bundle_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/5.0

Behavior5/5

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

Even with annotations already declaring readOnly/idempotent/non-destructive, the description adds substantial beyond-annotation context: no client/booking/hold/payment/receipt is created, input amounts and provider IDs are refused, the fingerprint is advisory and not a price lock, completeness requires details/invoice fields/consent, and later commands must revalidate. It also discloses the auth profile (clients:read plus family read, public_api key authority persists after reads) and that a quote does not reserve slots.

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 and endpoint are front-loaded, which is good, but the remainder is one dense semicolon-chained block with obscure operational asides ('Disabling headless new entry preserves authorized quote reads') that reduce scanability. It contains real signal but is over-packed and unstructured for its length.

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?

With no output schema, the description compensates well by describing return behavior (status=incomplete, missing_inputs, advisory fingerprint) and auth/side-effect requirements for a nested-body read tool. Remaining gaps are undeclared sub-parameters and a payment_source reference that does not appear in the schema, but nothing an agent needs to invoke it correctly is missing.

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 parameter meaning. It genuinely adds semantics for client_id (owned studio Client, requires clients:read, never visitor login, omit for anonymous), page/per_page (page file-transfer choices only, 1..100 bounds), consents (refund policy never requested for bundle) and invoice fields, but leaves tier_id, bundle_plan_id, promo_code and credit_choice enum values unexplained. Coverage is partial rather than complete.

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 opening states a specific verb and resource: 'Preview current customer bundle selections and checkout requirements' at POST /api/v2/bundle-purchases/quotes. It differentiates behaviorally from tour and subscription quote families via the consent and payment_source notes, but it never names the sibling quote tools (podyx_packages_bundle_quote, podyx_subscription_quote) to confirm which one an agent should pick.

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 usable context: omit client_id for anonymous preview, booking sessions are explicit and multi-session, and 'Studio Tour has its own published quote and booking operations' steers away from tour quoting. It falls short of explicit alternatives because it never names the sibling tools by name for the very similar bundle/package quote operations.

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

Deploy Server