Skip to main content
Glama

podyx_packages_subscription_rights

Read-onlyIdempotent

Retrieve a client's subscription rights and effective session lengths from purchased snapshots and current ledger allowance; quotes are advisory and read-only.

Instructions

Subscription rights GET /api/v2/clients/{id}/subscription-rights. 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>"
    },
    "name": "podyx_packages_subscription_rights"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds real value: it discloses the authority model (a live billing portal URL is only returned to a key holding current subscriptions:manage authority, while read-only keys see state without the live instruction) and negative capability boundaries (plan changes, pause and resume unsupported; paid external decline retains a refund obligation without executing a refund). Much of the remaining text describes redemption and cancellation semantics, which are not performed by this read-only route and add noise rather than transparency for this call.

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?

The text is a run-on sequence of unrelated facts, with sentences about redemption atomicity, cancellation routes, native provider delivery and refund obligations that do not apply to this GET endpoint. The one genuinely load-bearing clause for a reader ('Read/preview only', pagination) sits at the very end rather than being front-loaded.

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

Completeness3/5

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

For a two-parameter, nested read tool with no output schema, the description does convey the authority caveat and the read-only nature, which is meaningful. But it leaves the entire query parameter set unexplained and spends most of its length on sibling operations, so an agent still cannot tell what shape the returned rights data takes or how to scope the request.

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 query object carries seven undocumented fields: page, per_page, service_id, addons_page, addons_per_page, duration_minutes and member_package_id. The description only says 'Follow all pagination', which at best hints at page/per_page; it says nothing about service_id scoping, addon pagination or what duration_minutes/member_package_id affect. With zero schema coverage, the description needed to compensate and does not.

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 line identifies the resource and the underlying route ('Subscription rights GET /api/v2/clients/{id}/subscription-rights') and states the computation basis: purchased snapshots plus current ledger allowance determine rights and effective session lengths. It does not explicitly contrast itself with the close siblings podyx_packages_subscription_quote or podyx_packages_subscription_management, so the agent must infer the split, but the verb+resource is unambiguous.

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?

'Read/preview only' and 'Quotes are advisory' give implicit routing hints toward the quote siblings, and 'Follow all pagination' sets a usage obligation. However, there is no explicit statement of when to call this instead of podyx_packages_subscription_quote or podyx_packages_subscription_management, and no preconditions (e.g. does the client need an active subscription?) are stated.

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

Deploy Server

Other Tools