luma-events-mcp

get_guest

Retrieve a specific guest's data for a Luma event by event ID and guest ID. Returns guest details or an error if not found.

Instructions

Get a specific guest for a Luma event.

Args:
    event_id: The unique identifier of the event (e.g., "evt-ABC123")
    guest_id: The unique identifier of the guest

Returns:
    Guest data or an error message

Input Schema

TableJSON Schema

Name	Required	Description	Default
`event_id`	Yes
`guest_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions that guest data or an error message is returned; it does not state read-only intent, auth requirements, not-found behavior, or any side effects.

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?

The description is compact and well-structured: a clear leading purpose sentence, followed by Args and Returns sections with no filler. Every sentence contributes useful information.

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 simple retrieval tool with two required parameters and an output schema, the description covers the inputs and return. It lacks usage guidance and behavioral detail, but it is complete enough to invoke the tool correctly for its core purpose.

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 0%, so the description must compensate. It does add the semantic roles ('unique identifier of the event' and 'unique identifier of the guest') and an example format for event_id, but guest_id remains under-specified with no example or format hint.

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: get a specific guest for a Luma event. This clearly distinguishes it from sibling tools like get_guests or get_event, since it is scoped to one guest.

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?

The description implies when to use the tool: when a single guest is needed. However, it never explicitly contrasts it with sibling alternatives such as get_guests for listing all guests or get_all_past_guests, so an agent must infer the routing.

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

Deploy Server