Launchelion

Create a checkout link for a paid add-on

create_checkout

Create a Stripe checkout URL for one paid add-on on one listing, and return it for a HUMAN to open. Never present this as a completed purchase: nothing is charged until a person completes checkout in a browser. Returns an error when the listing doesn't exist, the add-on isn't purchasable yet (free early access), or payments aren't configured in this environment.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The listing's slug (as in a toolUrl, e.g. '/tools/acme-writer' -> 'acme-writer').
`product`	Yes	Add-on key: premium_launch, review_one, review_monthly, network_all, network_three. See list_offers for names, effects, and prices.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`error`	No
`checkoutUrl`	No	A URL a HUMAN must open. Nothing is charged until a person completes it.
`instruction`	No

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations, the description explains that nothing is charged until checkout is completed by a human and that errors occur for missing listings, non-purchasable add-ons, or unconfigured payments. This substantially clarifies the tool's operational behavior without contradicting the annotations.

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?

Three compact sentences each contribute directly: what is returned, what it does not mean, and what error conditions to expect. No filler or repeated schema information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition covers the key operational details an agent needs: who must complete the action, what the URL is not, and the relevant failure modes. An output schema exists, so the description does not need to reproduce return-value details.

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?

The schema already documents both parameters with 100% coverage, including the slug format and an enum for the product. The description adds only broad context about the operation being for one paid add-on on one listing, which is sufficient at baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete action ('Create a Stripe checkout URL') and a narrow scope ('for one paid add-on on one listing'), which clearly distinguishes it from sibling listing/search tools. It tells an agent exactly what resource is acted on and what artifact is produced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states when to call the tool: to produce a checkout URL for a human to complete a purchase. It also warns against presenting the result as a completed purchase and notes conditions that yield errors. However, it does not explicitly point to an alternative tool for cases like free early-access add-ons.

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

All Launchelion tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: searching listings, retrieving listing details, finding alternatives, viewing purchasable add-ons, creating a checkout, and submitting a tool. There is no meaningful overlap between any two tools, even though search and alternatives both relate to discovery, their inputs and outputs are clearly separated.

Naming Consistency5/5

All six tool names follow a consistent verb_noun snake_case pattern: create_checkout, get_tool, list_alternatives, list_offers, search_tools, submit_tool. The verb is always first and the resource focus is clear, making the toolset predictable and easy to navigate.

Tool Count5/5

Six tools is a well-scoped size for the server's purpose: discovering, retrieving, comparing, submitting, and optionally promoting AI tool listings. Each tool earns its place and there is no bloat or thinness.

Completeness5/5

The toolset covers the full public-facing lifecycle of the domain: search and discovery, detail retrieval, alternative lookup, submission of new tools, and monetization via offers and checkout. There are no obvious dead ends; the only intentionally external step is the human completing checkout, which is clearly documented.

Resources

Need Help?