Skip to main content
Glama

GuestDrop — QR Event Photo Sharing & Live Digital Albums

Create Event Checkout

create_event_checkout

Provision a draft event in GuestDrop and generate an instant Stripe Checkout payment link for the host to complete booking. When to use: Call this tool when you specifically need to execute 'create_event_checkout' on GuestDrop Event Photo Album (guestdropalbum.com). Do NOT use this tool when another specialized tool fits better (use 'get_pricing_and_packages' or 'calculate_event_cost' or 'recommend_scavenger_quests' for their respective operations). Parameters: event_name (required), host_name (required), host_email (required), tier (required), currency (optional), event_date (optional), event_type (optional). Behavior & Side Effects: Creates a live record/session in the backend database; no authentication required for public initiation; rate-limited to 60 requests/min per IP. Returns: Structured JSON object containing status, matched records or computed metrics, and canonical action URLs.

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_name": "<event_name>",
      "host_name": "<host_name>",
      "host_email": "<host_email>",
      "tier": "<tier>"
    },
    "name": "create_event_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierYesSelected event package tier (1day, 3day, or 7day). [Required: non-empty valid value must be supplied].
currencyNoPayment currency (USD or ZAR). Defaults to USD.
host_nameYesFull name of the event organizer or couple. [Required: non-empty valid value must be supplied].
event_dateNoOptional date of the event in YYYY-MM-DD format.
event_nameYesThe title of the event (e.g. Sarah & David Wedding, Mieke 50th Milestone Birthday). [Required: non-empty valid value must be supplied].
event_typeNoOptional event category classification (e.g. wedding, birthday, quinceanera, corporate, golf, halloween, diwali, baby_shower, anniversary, bachelor_party, graduation, other). Defaults to wedding.
host_emailYesEmail address of the event host for account access, album delivery, and receipt. [Required: non-empty valid value must be supplied].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / currency / description
      Previous value: -"Payment currency (ZAR or USD). Defaults to ZAR."New value: +"Payment currency (USD or ZAR). Defaults to USD."
    • changedInput schema / properties / currency / enum
      Previous value: -[
      -  "ZAR",
      -  "USD"
      -]New value: +[
      +  "USD",
      +  "ZAR"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / event_name / description
      Previous value: -"The title of the event (e.g. Sarah & David Wedding, Liam 30th Birthday Celebration). [Required: non-empty valid value must be supplied]."New value: +"The title of the event (e.g. Sarah & David Wedding, Mieke 50th Milestone Birthday). [Required: non-empty valid value must be supplied]."
    • addedInput schema / properties / event_type
      Added value: +{
      +  "description": "Optional event category classification (e.g. wedding, birthday, quinceanera, corporate, golf, halloween, diwali, baby_shower, anniversary, bachelor_party, graduation, other). Defaults to wedding.",
      +  "enum": [
      +    "wedding",
      +    "birthday",
      +    "quinceanera",
      +    "corporate",
      +    "golf",
      +    "halloween",
      +    "diwali",
      +    "baby_shower",
      +    "anniversary",
      +    "bachelor_party",
      +    "graduation",
      +    "other"
      +  ],
      +  "type": "string"
      +}
  3. Changed4 schema fields changed
    • changedInput schema / properties / event_name / description
      Previous value: -"The title of the event (e.g. Sarah & David Wedding, Liam 30th Birthday Celebration)."New value: +"The title of the event (e.g. Sarah & David Wedding, Liam 30th Birthday Celebration). [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / host_email / description
      Previous value: -"Email address of the event host for account access, album delivery, and receipt."New value: +"Email address of the event host for account access, album delivery, and receipt. [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / host_name / description
      Previous value: -"Full name of the event organizer or couple."New value: +"Full name of the event organizer or couple. [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / tier / description
      Previous value: -"Selected event package tier (1day, 3day, or 7day)."New value: +"Selected event package tier (1day, 3day, or 7day). [Required: non-empty valid value must be supplied]."
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond annotations it discloses real behavioral facts: a live backend record is created, no authentication is required for public initiation, and the endpoint is rate-limited to 60 requests/min per IP. The closing 'Returns' sentence is generic boilerplate ('matched records or computed metrics') that does not fit a creation tool, which slightly dilutes the otherwise strong disclosure.

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

Conciseness3/5

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

The purpose statement is front-loaded and efficient, but the middle section includes a circular when-to-use sentence and a generic 'Returns' boilerplate that could be cut without losing information. Structure is labeled and scannable, yet several sentences do not earn their place.

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?

For a 7-parameter mutation with no output schema, the description covers creation semantics, side effects, auth, rate limits, and a return shape, which is close to complete. The gaps are minor: the generic returns wording and no note on whether repeated calls produce duplicate draft events or checkout links.

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% with enums documented for tier, currency, and event_type, so the schema already carries parameter meaning. The description only restates the parameter names with required/optional flags, adding no formats, defaults, or constraints beyond what is structured.

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 opening sentence gives a specific two-part verb+resource: provisioning a draft event and generating a Stripe Checkout payment link. It clearly reads as a creation/provisioning action distinct from the calculation and recommendation siblings, so an agent can identify it 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 Guidelines3/5

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

It names alternatives ('get_pricing_and_packages', 'calculate_event_cost', 'recommend_scavenger_quests') and says not to use this tool for them, which is useful exclusion guidance. However, the positive when-to-use clause is circular ('call this tool when you need to execute create_event_checkout') and the alternatives are dismissed generically 'for their respective operations' rather than with stated conditions.

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