The AI Tools Index

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?

The description adds meaningful behavioral details beyond the annotations: no charge occurs until checkout is completed in a browser, the URL must be given to a human, and errors return for specific non-purchase cases. This does not contradict 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?

The description is three focused sentences: action and audience, payment caveat, and error conditions. Every sentence contributes without redundancy or filler.

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 two-parameter tool with a fully documented input schema and an output schema, the description covers purpose, human handoff, side effects, and failure modes. An agent has enough context to decide when to call it and what to expect.

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?

Schema coverage is 100%, so both parameters are already documented with examples and product enums. The description adds no extra parameter formatting, but it does reinforce the one-add-on/one-listing constraint.

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 states a clear action—create a Stripe checkout URL—scoped to one paid add-on on one listing, and explicitly says the result is for a human to open. This differentiates it from the sibling search/read/list tools.

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 establishes this is a human-facing checkout flow and that the agent must not present a URL as a completed purchase. It does not explicitly name alternatives for handling non-purchasable add-ons, but the error conditions and general context imply when it is not usable.

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

All The AI Tools Index 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.6/5.0

Disambiguation5/5

Each tool serves a clearly distinct purpose: searching, retrieving details, listing alternatives, viewing purchase offers, creating a checkout, and submitting a new tool. There is no overlapping functionality between any two tools, as even search vs. get_tool are layered (search returns summaries, get_tool returns full details).

Naming Consistency5/5

All tool names follow a uniform verb_noun pattern in snake_case: create_checkout, get_tool, list_alternatives, list_offers, search_tools, submit_tool. The pattern is immediately predictable and readable, with no mixed conventions or vague verbs.

Tool Count5/5

Six tools is ideal for this server's scope. It covers discovery (search, get, list alternatives), monetization (list offers, checkout), and content creation (submit), without any extraneous or redundant tools. Each tool earns its place.

Completeness4/5

The surface covers the core workflows for both buyers (search, retrieve details, see offers, purchase) and makers (submit a tool). The only minor gap is a lack of update/delete functionality for submitted listings, but that is outside the apparent intent for this server. The domain is well-covered.

Resources

Need Help?