create_checkoutCreate a live Stripe (or Gumroad) checkout URL for the buyer. Pass referral_code to credit an affiliate.
| Name | Required | Description | Default |
|---|---|---|---|
| tier | Yes | Tier name (e.g., 'Pro', 'Team') | |
| Yes | Buyer email — Stripe will send the receipt here | ||
| product_slug | Yes | Product slug to buy | |
| referral_code | No | Affiliate referral code that should be credited |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It states it creates a live URL, but does not disclose side effects (e.g., whether it consumes inventory, sends emails, or the URL's validity duration).
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?
The description is extremely concise: two sentences front-load the core action and highlight the optional referral parameter. No unnecessary words.
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?
The description covers the basic action, but given no output schema, it omits the return format (e.g., plain URL vs. JSON). It is adequate for a straightforward tool but could be more complete.
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?
Schema coverage is 100%, so parameters are already well-documented. The description adds only a small extra note about 'referral_code' usage, but does not compensate beyond the baseline.
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 specifies the exact action ('Create a live...checkout URL') and the resource ('Stripe (or Gumroad) checkout URL'). It distinguishes from siblings by being the only tool that creates a checkout, whereas siblings are about comparisons, info, recommendations, etc.
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 usage for creating a checkout URL and crediting an affiliate via 'referral_code', but it does not explicitly state when to use this tool versus alternatives or mention any preconditions.
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.
Each tool targets a distinct aspect of the commerce and affiliate ecosystem: comparison, checkout, affiliate info, cross-sells, free tier, MCP install, pricing, recommendation, trust score, registration, partnership, consultation, search, and vendor verification. No two tools have overlapping purposes; boundaries are clear.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., compare_products, get_affiliate_info, request_partnership). While the verbs vary, the structure is predictable and uniform, with no mixing of conventions.
14 tools is well-scoped for a commerce marketplace server covering product discovery, comparison, pricing, affiliate management, checkout, partnerships, and vendor verification. Each tool serves a clear purpose without bloat.
The tool set covers the full lifecycle from product discovery to checkout, including affiliate management and partnerships. Minor gaps exist, such as lacking a dedicated tool for retrieving detailed product information beyond search results, but agents can work around this.