MCC Solutions

Get a checkout link for a store product

get_checkout_link

Read-onlyIdempotent

Return the secure checkout link for one MCC store product (by the slug from search_store). The person completes the purchase themselves on that page: they enter their email, accept the terms and pay by card through Stripe. Nothing is charged by calling this tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_checkout_link"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Product slug from search_store

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent, and the description adds genuinely new context: the human completes the purchase on the returned page via Stripe, and 'Nothing is charged by calling this tool.' That pre-empts the main misreading of a checkout-link tool. It doesn't mention link expiry or reuse limits, which would be the remaining useful detail.

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 short sentences, front-loaded with what is returned and scoped to one product, followed by the human-side flow and the no-charge disclaimer. No filler or restated name/title.

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 one-parameter read tool with no output schema, the description covers the return value, the downstream user action, the payment processor, and the cost behavior. Nothing an agent needs to call it correctly or explain the result to a user is missing.

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% and the single slug parameter is already documented as 'Product slug from search_store', so the description adds essentially no new parameter meaning. Baseline of 3 applies when the schema carries the semantics.

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?

States a specific verb and resource ('Return the secure checkout link') scoped to 'one MCC store product', which distinguishes it from catalog-style siblings such as search_store or get_services_and_prices. An agent knows exactly what it receives without opening the schema.

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 phrase 'by the slug from search_store' tells the agent this is a follow-on step after search_store, giving clear usage context. It does not state when not to call it or name an alternative checkout path, so it falls short of explicit exclusions.

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

All MCC Solutions tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?