Skip to main content
Glama

list_purchases

Retrieve your purchased digital products from the402.ai marketplace to view download status and manage acquired services.

Instructions

List your purchased digital products on the402.ai. Shows products you've bought with download status. Requires API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'list_purchases' tool is registered and implemented directly in 'src/tools/products.ts' using the McpServer instance. It calls 'client.authGet("/v1/purchases")' to retrieve the list of purchased products.
    server.tool(
    	"list_purchases",
    	"List your purchased digital products on the402.ai. Shows products you've bought with download status. Requires API key.",
    	{},
    	async () => {
    		const result = await client.authGet("/v1/purchases");
    		return {
    			content: [
    				{ type: "text" as const, text: JSON.stringify(result, null, 2) },
    			],
    		};
    	}
    );
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the requirement 'Requires API key' for authentication and hints at behavior by mentioning 'download status', which adds context beyond a basic list. However, it lacks details on rate limits, pagination, error handling, or whether this is a read-only operation (implied by 'List' but not explicit).

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

Conciseness5/5

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

The description is front-loaded with the core purpose in the first sentence, followed by additional context and a requirement. Every sentence earns its place: the first defines the action, the second adds scope, and the third specifies prerequisites. It's efficient with no wasted words, making it easy for an AI agent to parse quickly.

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?

Given no annotations, no output schema, and zero parameters, the description provides basic completeness by stating purpose, scope, and authentication needs. However, for a tool that likely returns a list of purchases, it doesn't explain return values (e.g., format, fields like product names or dates), which could be helpful since there's no output schema. It's adequate but has gaps in behavioral context.

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?

The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add parameter-specific information, which is appropriate here. Baseline is 4 for zero parameters, as there's nothing to compensate for and the description doesn't introduce confusion.

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 description clearly states the verb 'List' and resource 'purchased digital products on the402.ai', specifying scope with 'Shows products you've bought with download status'. It distinguishes from sibling tools like 'browse_products' and 'search_catalog' by focusing on user purchases rather than general catalog browsing. However, it doesn't explicitly contrast with 'purchase_product' or 'verify_delivery', which are related but distinct operations.

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?

The description implies usage context by stating 'Requires API key' and focusing on user purchases, suggesting it's for viewing purchase history rather than browsing or buying. However, it doesn't explicitly state when to use this tool versus alternatives like 'balance_history' for financial tracking or 'verify_delivery' for delivery status, nor does it provide exclusions or prerequisites beyond the API key.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/the402ai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server