Podyx MCP

podyx_addon_quote

Read-onlyIdempotent

Preview a customer's addon selections and checkout requirements to see missing inputs, configured forms and consent documents. Returns advisory facts only; creates no booking, hold, payment or price lock.

Instructions

Preview current customer addon selections and checkout requirements POST /api/v2/addon-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_addon_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?

Beyond the readOnly/idempotent/non-destructive annotations, it discloses what is destroyed or created (nothing: no client, booking, hold, payment or receipt), that Podyx resolves pricing and refuses client-supplied amounts or provider IDs, that the fingerprint is advisory and not a price lock, and that later commands must revalidate. It also names the auth requirements (clients:read plus the family read permission, and existing API-key authority surviving reads).

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 in the first sentence, but the body degenerates into a dense stream of fragment clauses and endpoint jargon. Several sentences (headless entry, recording seats, published consent documents) are borderline noise, and the lack of any structure makes the constraints hard to scan.

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 nested-body preview tool with no output schema, the description covers the important behavioural contract: incomplete results, missing_inputs, advisory fingerprints, and permission requirements. It stops short of describing any successful response shape or the meaning of the array and choice parameters, which leaves a small residual gap.

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 prose carries real weight, and it does explain client_id semantics (owned studio Client, never visitor login), the page/per_page 1..100 bounds, consent expectations, and invoice fields. However, nested fields such as addons/addon_id/quantity, slot_id, and credit_choice receive no explanation anywhere, leaving a meaningful compensation gap.

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?

The opening states a concrete verb and resource: preview addon selections and checkout requirements via POST /api/v2/addon-purchases/quotes. It explicitly separates this from the sibling quote families (bundle, subscription, Studio Tour), so an agent can pick it without opening another schema.

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?

It gives concrete selection rules: omit client_id for an anonymous preview, email is not accepted here, follow all pagination, and a quote never reserves a slot or holds a price. It also notes Studio Tour has its own quote operations. What it lacks is an explicit 'use podyx_bundle_quote / podyx_subscription_quote instead when...' routing statement for the neighbouring quote tools.

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

Deploy Server