Skip to main content
Glama

Pagetool

Create payment link

purchase_link
Destructive

Creates the one Stripe Checkout link that pays for a domain registration and saves the card of the customer, so every later purchase can happen inside this conversation. This is the only time the user leaves the chat - give them the returned URL. Reach for this only after they have asked to publish. A refused or unchecked domain ending carries reason and a plain reason_text: unsupported or price_unavailable mean we do not sell that ending right now; lookup_failed or cap_reached mean it was NOT checked, so search again, and never tell the customer we do not sell it.

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": {
      "domain": "<domain>"
    },
    "name": "purchase_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe full domain to buy, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag this as a non-readonly, destructive, open-world, non-idempotent call, so the safety profile is largely covered. The description still adds real value beyond them: card capture for later purchases, the fact that this is the only point where the user leaves the chat, and a protocol for interpreting refusal reasons. It stops short of saying whether the customer is charged immediately versus only on checkout completion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the user-leaves-chat instruction are front-loaded, and the precondition follows. The final sentence on reason codes is dense and long, but every clause is an actionable branch an agent must handle, so little is wasted.

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

Completeness4/5

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

There is no output schema, and the description compensates by naming the returned URL and the 'reason'/'reason_text' fields the caller must interpret. For a one-parameter tool with annotations present this is nearly complete; only the success-path charge semantics remain unstated.

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% for the single 'domain' parameter, so the schema already carries the baseline. The description's domain-related detail concerns failure reasons on the ending rather than adding syntax or format meaning to the parameter itself, so the baseline 3 applies.

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 ('Creates the one Stripe Checkout link that pays for a domain registration') and adds the key side effect ('saves the card of the customer'). It also draws the boundary against the many other purchase/publish siblings by tying the tool to the final payment step rather than to search or execution.

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

Usage Guidelines5/5

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

Gives an explicit gating condition ('Reach for this only after they have asked to publish') and an explicit handoff instruction ('give them the returned URL'). It also routes error cases: 'lookup_failed or cap_reached mean it was NOT checked, so search again,' which effectively names the alternative action when the precondition fails.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources