VenuNite Events

Create Ticket Handoff

create_ticket_handoff

Create an attributed VenuNite ticket handoff for a specific event_id. Requires a live API key issued at https://venunite.com/developers/keys. Returns a preview-safe handoff_url; leaving for seller checkout requires the user to explicitly select Continue. This tool records a handoff but does not purchase, reserve, hold inventory, guarantee availability or final prices, or confirm a booking. Calls count against normal MCP tool-call limits; no search-result rows are charged. The handoff service also limits creation to 10 per minute per account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`event_id`	Yes	The stable VenuNite event_id returned by search_events.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "booking_mode": {
-        "const": "external_checkout"
-      },
-      "event_id": {
-        "maximum": 2147483647,
-        "minimum": 1,
-        "type": "integer"
-      },
-      "event_url": {
-        "format": "uri",
-        "pattern": "^https://venunite\\.com/events/[^/?#]+$",
-        "type": "string"
-      },
-      "expires_at": {
-        "format": "date-time",
-        "type": "string"
-      },
-      "handoff_id": {
-        "maxLength": 128,
-        "minLength": 1,
-        "type": "string"
-      },
-      "handoff_url": {
-        "format": "uri",
-        "pattern": "^https://venunite\\.com/tickets/handoff/[A-Za-z0-9_-]{43}$",
-        "type": "string"
-      },
-      "requires_user_action": {
-        "const": true
-      }
-    },
-    "required": [
-      "handoff_id",
-      "event_id",
-      "event_url",
-      "handoff_url",
-      "expires_at",
-      "booking_mode",
-      "requires_user_action"
-    ]
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "error",
-      "message"
-    ]
-  }
-]New value: +[
+  {
+    "properties": {
+      "booking_mode": {
+        "const": "external_checkout"
+      },
+      "event_id": {
+        "maximum": 2147483647,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "event_url": {
+        "format": "uri",
+        "pattern": "^https://venunite\\.com/events/[^/?#]+$",
+        "type": "string"
+      },
+      "expires_at": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "handoff_id": {
+        "maxLength": 128,
+        "minLength": 1,
+        "type": "string"
+      },
+      "handoff_url": {
+        "format": "uri",
+        "pattern": "^https://venunite\\.com/tickets/handoff/[A-Za-z0-9_-]{43}$",
+        "type": "string"
+      },
+      "requires_user_action": {
+        "const": true
+      }
+    },
+    "required": [
+      "handoff_id",
+      "event_id",
+      "event_url",
+      "handoff_url",
+      "expires_at",
+      "booking_mode",
+      "requires_user_action"
+    ]
+  },
+  {
+    "properties": {
+      "error": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "message"
+    ]
+  }
+]

AddedSep 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the API-key auth requirement, the 10-per-minute per-account rate limit, the billing behavior (counts against tool-call limits, no search-result charges), and the exact side-effect boundary (no purchase, reserve, hold, availability guarantee, or booking confirmation). This is precisely the extra context annotations cannot carry.

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?

Front-loads the core action and resource, then layers auth, return value, side-effect disclaimer, and limits in tight sentences. Every sentence carries distinct information; nothing is redundant with the name or schema.

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 an output schema present, the description need not explain return values, yet it still flags handoff_url as preview-safe. Auth, rate limits, billing, and side-effect boundaries are all covered, leaving no gap an agent needs before calling.

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% and event_id is fully documented in the schema as the stable ID returned by search_events. The description only echoes that it must be a 'specific event_id', adding no format or constraint detail beyond the structured field, 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 (create) and resource (attributed VenuNite ticket handoff) scoped to an event_id. The reader can immediately separate it from the sibling search_events, which only retrieves events.

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?

Gives clear preconditions (live API key, user must explicitly select Continue) and a firm scope boundary (records a handoff, does not purchase/reserve/hold/confirm). It never explicitly names search_events as the alternative or states when not to call it, so it falls short of a 5.

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

All VenuNite Events 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?