Leitura de assinaturas na Kiwify. Ações:
list: lista assinaturas (filtros: product_id, status, page_size, page).
get: detalhe de UMA assinatura (requer subscription_id).
[Flattened action: get]
Bulk support: accepts subscription_ids, product_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| status | No | ||
| account | No | ||
| page_size | No | ||
| product_id | No | ||
| product_ids | No | ||
| subscription_id | No | ||
| subscription_ids | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly and idempotent. Description adds two-action behavior but lacks details on pagination, ordering, or error handling beyond what annotations imply.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is brief with sections; efficient use of words, though 'Flattened action: get' may confuse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema; description does not explain return values for list vs get, pagination details, or parameter formats (e.g., how to specify dates?). Missing completeness for a dual-action tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema coverage, description explains several parameters in context (product_id, status, page_size, page, subscription_id, bulk ids) but omits 'account' parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states reading subscriptions with list and get actions, but the tool name suggests only get. It is somewhat clear but does not differentiate from sibling 'kiwify_subscriptions_list' tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides context for list vs get filters but no explicit guidance on when to use this tool versus sibling tools like 'kiwify_subscriptions_list' or 'kiwify_subscriptions_write_cancel'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.