Podyx MCP

podyx_get_member_bundle

Read-onlyIdempotent

Read a purchased member bundle by ID to review plan terms, included add-ons, usage counters, and paginated session totals; requires purchases, payments, and sessions read scopes.

Instructions

Member bundle GET /api/v2/member-bundles/{id}. Read a purchased Member Bundle by member_bundle_id, not an API purchase ID or catalog plan ID. Requires purchases:read, payments:read and sessions:read. Includes active, pending, exhausted, expired, cancelled and declined purchases, including historical/admin grants with no API purchase or payment. plan_snapshot preserves sold names, terms and add-on prices; included_addons uses the purchased version and current add-on display/one-off consumption, as the CMS does. Usage counters and reconciliation totals cover the complete consuming-session set; page/per_page paginate that set, ordered by studio-local date, time and session ID. Cancelled/deleted sessions do not hold units; unlinked/excess units disclose counter disagreement without inventing its cause. Pricing follows the CMS purchase breakdown; itemized=false means legacy fallback, not a captured itemized quote. Payment settlement, fulfillment and purchased status remain distinct; external money reports actual collection/refund coverage. Unknown or foreign IDs return 404. No provider calls, payment capabilities, private metadata or promo code text are returned. 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>"
    },
    "name": "podyx_get_member_bundle"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the read-only annotation by listing required scopes, included purchase states, historical/admin-grant behavior, pagination ordering, session-unit rules, pricing fallback semantics, settlement distinctions, and 404 behavior. It also clarifies what is not returned, such as provider calls, payment capabilities, private metadata, and promo code text.

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

Conciseness4/5

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

The purpose and ID distinction are front-loaded, and the remaining sentences add behavioral detail rather than filler. The description is dense and could be easier to scan with bullets, but most of its length is justified by the tool's complex domain semantics.

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

Completeness5/5

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

For a complex read tool with no output schema, the description covers permissions, included statuses, snapshot and add-on semantics, pagination behavior, pricing caveats, error behavior, and excluded return data. It gives enough context for an agent to call it correctly and interpret key results.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the semantic burden. It explains that the path ID is a member_bundle_id rather than an API purchase or catalog plan ID, and that page/per_page paginate the complete consuming-session set in studio-local date/time/session-ID order; it does not define pagination defaults or limits beyond the schema minimums.

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?

States a specific read operation for a purchased Member Bundle and explicitly distinguishes member_bundle_id from API purchase IDs and catalog plan IDs. This lets an agent separate it from sibling purchase and plan retrieval tools.

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?

Explains the key usage condition: read a purchased bundle by member_bundle_id, not an API purchase ID or catalog plan ID. It also says to follow pagination and warns that a quote does not reserve a slot or lock a price, but it does not explicitly name the sibling tools to use for the excluded ID types.

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

Deploy Server