Podyx MCP

podyx_packages_bundle_quote

Read-onlyIdempotent

Generates an advisory bundle quote for a client using purchased snapshots and ledger allowance, showing package rights and effective session lengths without reserving a slot or locking a price.

Instructions

Bundle quote POST /api/v2/clients/{id}/bundle-redemptions/quotes. Package kind is fixed by the route. Purchased snapshots and current ledger allowance determine rights and effective session lengths. Quotes are advisory. Redemption atomically creates all sessions and required delivery intents, or writes nothing. Paid extras use the existing separate session add-on purchase flow. Current authority is checked on replay. Cancellation uses the existing subscription cancellation routes. Native provider work is deferred; management GET exposes pending, ready or failed delivery. A ready billing portal URL is disclosed only to a key with current subscriptions:manage authority; read-only keys retain state and capability visibility without the live instruction. Plan changes, pause and resume are unsupported. Paid external decline retains an actionable refund obligation without executing a refund. 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_packages_bundle_quote"
  }
}

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

C2.9/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world, and the description adds genuinely non-obvious behavior: quotes are advisory, do not reserve a slot or lock a price, and the billing portal URL is only disclosed to keys holding subscriptions:manage authority while read-only keys see state only. A few sentences (atomic redemption, refund obligations on decline) describe adjacent tools rather than this one, which slightly blurs the tool's own behavior.

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

Conciseness2/5

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

It is front-loaded with the route, which is good, but the remainder is a run-on series of comma-spliced fragments covering redemptions, cancellations, refunds, delivery states, and plan changes — much of it irrelevant to a quote call. The few sentences that do matter (advisory, no price lock, pagination) are buried at the end.

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

Completeness2/5

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

With no output schema and a nested two-parameter body, the description should explain what a quote returns (price breakdown, rights, effective session lengths) and what each body field means; it gestures at rights and session lengths but never gives an actionable answer. The authority and delivery-state notes are informative context but do not fill the gap for invoking this specific endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the nested body has seven undocumented fields (date, setup_id, start_time, member_package_id, recording_seats, duration_minutes, selected_one_off_addon_ids), yet the description explains none of them. The only partial cues are "Package kind is fixed by the route" and the advisory/no-price-lock note; the rest of the parameter meaning must be reverse-engineered from field names and formats.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ("Bundle quote") and gives the exact route, from which an agent can infer this previews a package bundle redemption cost. But it never states the verb plainly or distinguishes this from the near-identically named siblings podyx_bundle_quote and podyx_packages_subscription_quote, leaving the agent to guess which quote tool to pick.

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?

Several usage boundaries are implied: quotes are advisory, paid extras go through the separate session add-on purchase flow, cancellation uses subscription cancellation routes, and plan changes/pause/resume are unsupported. Useful, but they mostly describe sibling tooling rather than saying when to call this quote instead of the other 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