pifini

Create ticket checkout link

create_ticket_checkout

Create a secure Stripe-hosted payment link for event tickets. Returns a checkout URL — give it to the human to complete payment themselves; each ticket is then emailed with its QR code and its own link, which opens on any phone and can be saved to WhatsApp. Get ticket_type_id values from get_event. Always confirm the exact tickets and total with the human before calling this.

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": {
      "event_slug": "<event_slug>",
      "items": "<items>",
      "buyer_email": "<buyer_email>"
    },
    "name": "create_ticket_checkout"
  }
}

Input Schema

Name	Required	Description
`items`	Yes	Ticket selections
`buyer_name`	No	Buyer's name (optional)
`event_slug`	Yes	Event slug
`buyer_email`	Yes	Email to deliver tickets to (required — ask the human)

Output Schema

Name	Required	Description	Default
`event`	No
`total`	No
`currency`	No
`order_id`	No
`checkout_url`	No
`instructions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "checkout_url": {
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "event": {
+      "type": "string"
+    },
+    "instructions": {
+      "type": "string"
+    },
+    "order_id": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedJul 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: the payment link is Stripe-hosted, the human completes payment themselves, and each ticket is emailed with a QR code and phone-friendly link. This explains side effects and follow-up behavior. The annotations are generic and do not contradict the description.

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 well-structured sentences: the main action, the return/behavior, and the required human-confirmation step. Every sentence earns its place, and no information is wasted or buried.

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?

The description covers the core workflow: create the link, hand it to the human, and know what happens after payment. It also includes the critical prerequisite and confirmation step. It could have explicitly tied event_slug to get_event as well, but the schema and output schema cover the remaining details sufficiently.

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 description coverage is 100%, so the schema already documents all four parameters and their roles. The description repeats the 'ticket_type_id from get_event' guidance already present in the schema and adds no new parameter syntax, format, or source details beyond that. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Create a secure Stripe-hosted payment link for event tickets.' It clearly distinguishes the tool from the sibling get/search tools, and the return value (checkout URL) is stated explicitly. An agent can immediately tell what the tool accomplishes.

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 gives clear usage context: get ticket_type_id values from get_event, and always confirm exact tickets and total with the human before calling. It does not explicitly state when not to use this tool or name alternatives, but no close alternative exists among the siblings, so the guidance is sufficient.

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

All pifini 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?