Lanzamientos IA

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.5/5.0

Behavior5/5

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

The description adds meaningful behavior beyond the annotations: nothing is charged until the human completes checkout in a browser, the URL must be opened by a human, and money is never taken just by calling the tool. It also explains the main error conditions caused by missing listings, free early access, or unconfigured payments.

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 sentences with no wasted words: the first states the action, the second gives the critical no-charge caveat, and the third lists the main failure conditions. Every part of the description earns its place and important guidance is front-loaded.

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?

For a small tool with an output schema, this description is sufficient. It covers the action, the intended usage flow, the cost behavior, the failure modes, and the fact that this is an open-world action requiring human involvement. An agent has enough information to select and call the tool correctly.

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 input schema already documents both parameters at 100% coverage, so the description is not required to re-explain them. The description adds a small amount of semantic context by saying 'one paid add-on on one listing', but it does not materially expand on the schema's existing parameter descriptions.

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?

Clearly identifies a specific action (create a Stripe checkout URL), the unique resource (one paid add-on on one listing), and the intended recipient of the result (a human). It distinguishes itself from sibling list/search tools, which are about discovery rather than checkout creation.

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?

The description clearly states when to use the tool and importantly when not to: never present this as a completed purchase, and it fails when the add-on is not purchasable yet. However, it does not explicitly name an alternative sibling like list_offers for discovering which add-ons are purchasable, so it falls just short of full routing guidance.

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

All Lanzamientos IA 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 action: searching, retrieving details, listing alternatives, listing offers, creating a checkout, and submitting a new tool. Descriptions clearly differentiate search_tools from list_alternatives (free-text vs. named competitor) and get_tool (specific slug lookup), so an agent can reliably choose the right one.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (create_checkout, get_tool, list_alternatives, list_offers, search_tools, submit_tool). The verbs are distinct and meaningful, making the API highly predictable.

Tool Count5/5

Six tools is well-scoped for a server that handles discovery, submission, and paid promotion for AI tool listings. Each tool serves a clear purpose without redundancy, and the count feels appropriate for the domain's complexity.

Completeness5/5

The tool surface covers the primary user journeys: finding tools (search_tools), examining a specific tool (get_tool), comparing alternatives (list_alternatives), understanding promotional offers (list_offers), purchasing an offer (create_checkout), and adding new tools (submit_tool). There are no obvious dead ends, and the workflow from discovery to purchase to submission is fully supported.

Resources

Need Help?