add_guestAdd a guest to a live event's guest list — name, optional email, phone, category (e.g. vip/press), plus-ones, note, tags, and an optional ticket tier. Counts against the weekly invite limit. Requires event_id; you must be a host.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| tags | No | ||
| No | |||
| phone | No | ||
| category | No | ||
| event_id | Yes | ||
| last_name | No | ||
| first_name | Yes | ||
| ticket_class_id | No | ||
| plus_ones_allowed | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds behavioral context beyond annotations (invite limit, host requirement) but annotations already indicate non-destructive mutation. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no fluff, front-loads purpose and key parameters with essential behavioral notes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers purpose, key parameters, and constraints. No output schema means less to explain, but could mention success response or error cases. Mostly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Lists parameters and gives example for category, but with 0% schema coverage, more detail (e.g., formats of tags, plus_ones_allowed) would help. Adequate but not comprehensive.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the verb 'Add' and resource 'guest to a live event's guest list', listing key parameters and distinguishing from siblings like edit_guest, remove_guest, check_in_guest.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides important context: counts against weekly invite limit and requires host role. No explicit when-not-to-use, but context implies usage constraints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.