Podyx MCP

podyx_v1_list_addons

Read-onlyIdempotent

List add-ons for the authenticated studio with pagination and optional inactive items; review add-on availability and prices without reserving slots or locking prices.

Instructions

listAddons GET /api/v1/addons. The authenticated key resolves the studio. Tenant selectors supplied in the request are ignored. Lists default to page 1 and 20 entries; page sizes are capped at 100. Read/preview only. Follow all pagination; a quote does not reserve a slot or lock a price.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "podyx_v1_list_addons"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations it adds genuinely useful behavior: the authenticated key resolves the studio and tenant selectors in the request are ignored, which is a material tenancy constraint an agent cannot infer from annotations. It also discloses pagination defaults and the 100-item cap. It stops short of describing the shape of returned addon records.

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?

Front-loaded with the operation and endpoint, then tenancy, then pagination — a sensible order with little waste. The closing sentence bundles two unrelated ideas (pagination exhaustion and quote non-reservation), which is slightly awkward but still short.

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 simple, parameter-light list tool with no output schema, the definition covers the things an agent most needs: tenancy scoping, pagination protocol, and safety posture. The remaining gap is what a returned addon record contains and what include_inactive does, both minor for a listing call.

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 effectively 0% for the nested query object (only per_page carries 'Clamped to 1–100'), so the description does real work by supplying page default 1, per_page default 20, and the 100 cap. It says nothing about include_inactive, which is the one parameter whose semantics remain undocumented in both places.

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?

States a specific verb and resource ('listAddons GET /api/v1/addons') so the operation is unambiguous, and it is clearly the plural counterpart to sibling podyx_get_addon. It does not explicitly name which sibling to prefer over other addon-related tools (podyx_list_addon, podyx_v1_reports_addons), so the sibling differentiation is only implicit.

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?

It establishes the read/preview context and warns that a quote does not reserve a slot or lock a price, which nudges the agent toward quote tools for pricing decisions. However, it never states when to use this rather than podyx_list_addon or podyx_v1_reports_addons, and no prerequisites or exclusions are given.

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

Deploy Server