IA Selecta

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

Behavior5/5

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

Despite annotations already indicating this is a non-read operation, the description adds crucial behavioral context: no charge occurs until the human completes checkout in a browser, and errors arise for nonexistent listings, un-purchasable free early access, and unconfigured payments. This goes well beyond 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 3 sentences with no fluff. The main operation is front-loaded, the critical purchase-completion caveat follows immediately, and the failure modes are compactly enumerated at the end.

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?

With only 2 parameters, full schema documentation, and an output schema, the description covers all essential behavior: what it does, how to interpret the result, and when it fails. No meaningful gaps exist for an agent to call the tool correctly.

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 schema already provides full documentation for both parameters (100% coverage), including an enum and a slug example. The description adds value by framing the product as 'paid add-on' and clarifying it applies to exactly one listing, plus tieing error conditions to the parameters.

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 specific action and resource: 'Create a Stripe checkout URL for one paid add-on on one listing.' This clearly distinguishes it from sibling tools like get_tool and list_offers, which are read-oriented.

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?

Clear context is provided: the result is for a human to open, and it must not be presented as a completed purchase. Error conditions are also listed. It stops short of explicitly naming alternatives or stating 'use list_offers to inspect add-on options before checking out' in the main description.

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

All IA Selecta 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.4/5.0

Disambiguation4/5

Most tools are clearly distinct: create_checkout, get_tool, list_alternatives, list_offers, search_tools, and submit_tool serve different purposes. However, list_alternatives and search_tools could be confused when searching for alternatives, but their descriptions clarify the target types (well-known tool slug vs. free-text query).

Naming Consistency4/5

Tool names follow a fairly consistent verb_noun pattern: create_checkout, get_tool, list_alternatives, list_offers, search_tools, submit_tool. The only minor deviation is that get_tool is singular while list_* are plural, but this is not a significant inconsistency.

Tool Count5/5

6 tools is well-scoped for a marketplace/directory server with search, detail retrieval, alternatives, paid promotions, and submission. Each tool serves a necessary function without redundancy or bloat.

Completeness4/5

The core workflows are covered: search and view details, list and purchase add-ons, and submit a listing. Minor gaps exist—no update/delete for listings or offers, and no way to manage claims—but these are administrative features outside the main agent use case.

Resources

Need Help?