Lists the account's purchases with their state.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| total | Yes | How many purchases the account has. | |
| purchases | Yes | The purchases, from the most recent to the oldest. |
Changes observed during successful MCP inspections.
Output schema / properties / purchases / descriptionPrevious value: -"Las compras, de la más reciente a la más antigua."New value: +"The purchases, from the most recent to the oldest."Output schema / properties / purchases / items / properties / amountUsd / descriptionPrevious value: -"Lo que se pagó, en USD, como NÚMERO (forma antigua)."New value: +"What was paid, in USD, as a NUMBER (old form)."Output schema / properties / purchases / items / properties / amountUsdDecimal / descriptionPrevious value: -"Lo MISMO como cadena decimal: la forma canónica."New value: +"The SAME as a decimal string: the canonical form."Output schema / properties / purchases / items / properties / canOpenDispute / descriptionPrevious value: -"Todavía se puede abrir una disputa."New value: +"A dispute can still be opened."Output schema / properties / purchases / items / properties / disputeWindowUntil / descriptionPrevious value: -"Fin CIERTO del plazo de disputa (ISO); null si no se sabe con certeza."New value: +"CERTAIN end of the dispute window (ISO); null if it is not known for sure."Output schema / properties / purchases / items / properties / downloadable / descriptionPrevious value: -"Hay archivo que descargar."New value: +"There is a file to download."Output schema / properties / purchases / items / properties / inDispute / descriptionPrevious value: -"La orden está EN disputa ahora mismo."New value: +"The order is IN dispute right now."Output schema / properties / purchases / items / properties / license / descriptionPrevious value: -"Licencia de la PLANTILLA: standard o exclusive."New value: +"License of the TEMPLATE: standard or exclusive."Output schema / properties / purchases / items / properties / orderId / descriptionPrevious value: -"Uuid de la orden cripto (null si no se pagó en cripto); lo piden las herramientas de disputa."New value: +"Uuid of the crypto order (null if it was not paid in crypto); the dispute tools ask for it."Output schema / properties / purchases / items / properties / paidByAgent / descriptionPrevious value: -"Nombre del agente delegado que la pagó con su wallet; null si la pagó la cuenta."New value: +"Name of the delegate agent that paid it with its wallet; null if the account paid it."Output schema / properties / purchases / items / properties / paymentMethod / descriptionPrevious value: -"Con qué se pagó."New value: +"What it was paid with."Output schema / properties / purchases / items / properties / purchaseId / descriptionPrevious value: -"Identificador de la COMPRA: es lo que pide `download`."New value: +"Identifier of the PURCHASE: it is what `download` asks for."Output schema / properties / purchases / items / properties / purchasedAt / descriptionPrevious value: -"Fecha de la compra (ISO)."New value: +"Date of the purchase (ISO)."Output schema / properties / purchases / items / properties / refunded / descriptionPrevious value: -"La orden acabó reembolsada."New value: +"The order ended up refunded."Output schema / properties / purchases / items / properties / sha256 / descriptionPrevious value: -"Huella SHA-256 del archivo (null si aún no está calculada)."New value: +"SHA-256 fingerprint of the file (null if it is not computed yet)."Output schema / properties / purchases / items / properties / support / descriptionPrevious value: -"Contacto de soporte del vendedor."New value: +"Support contact of the seller."Output schema / properties / purchases / items / properties / support / properties / email / descriptionPrevious value: -"Correo de soporte."New value: +"Support email."Output schema / properties / purchases / items / properties / support / properties / url / descriptionPrevious value: -"Página de soporte."New value: +"Support page."Output schema / properties / purchases / items / properties / template / descriptionPrevious value: -"La plantilla comprada."New value: +"The purchased template."Output schema / properties / purchases / items / properties / template / properties / name / descriptionPrevious value: -"Nombre en el idioma del token."New value: +"Name in the token's language."Output schema / properties / purchases / items / properties / template / properties / slug / descriptionPrevious value: -"Slug de la plantilla."New value: +"Slug of the template."Output schema / properties / total / descriptionPrevious value: -"Cuántas compras tiene la cuenta."New value: +"How many purchases the account has."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry behavioral disclosure. It conveys that the operation is a read-only list and that each purchase has a state, but it does not describe possible state values, ordering, pagination, or whether only completed purchases are included. This is acceptable for a simple list but not richly transparent.
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?
One short sentence with no filler. It front-loads the resource and the action, and every word contributes to the agent's understanding.
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?
Given zero parameters and the presence of an output schema, the description is sufficient to invoke the tool correctly. The word 'state' is slightly under-specified, but because an output schema exists, the description does not need to enumerate return fields or state values.
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?
The tool has zero parameters and the schema is fully covered (100%), so the baseline of 4 applies. The description adds the only meaningful semantic context: purchases are scoped to the account and include their state, which is genuinely useful beyond the empty schema.
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?
The description clearly identifies the resource ('the account's purchases') and states what is returned ('their state'), using the verb 'Lists' to indicate read-only retrieval. It does not explicitly distinguish from close siblings like my_sales or my_cart, but the account-scoped 'purchases' resource is unambiguous enough for selection.
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?
The description implies use when the caller needs a list of purchases for the current account, but gives no explicit conditions, exclusions, or alternatives. With many account-related sibling tools, an agent must infer when this one is the right choice rather than being told.
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.