Skip to main content
Glama

add_guest

Add a new guest group or household to your wedding guest list by entering the primary guest's first and last name. Optionally include a plus-one, email, phone, and affiliation.

Instructions

Add a new guest group (household) to the guest list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoGuest email address
phoneNoGuest phone number
last_nameYesPrimary guest last name
first_nameYesPrimary guest first name
affiliationNoAffiliation (default: PRIMARY_FRIEND)
plus_one_last_nameNoPlus-one last name
plus_one_first_nameNoPlus-one first name
Behavior3/5

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

Annotations already indicate destructiveHint=false, so the description adds minimal behavioral context. It clarifies that the tool creates a 'guest group (household)', which is useful but does not disclose side effects, authentication requirements, or what happens upon success.

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 a single sentence that efficiently conveys the core purpose. It is front-loaded with the verb and resource, with no redundant or misleading information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description covers the basic purpose, it does not mention return values, error conditions, or relevant side effects. Given the tool has 7 parameters, a moderate complexity, and no output schema, more completeness would be helpful.

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 coverage is 100%, so the input schema already documents all parameter meanings. The description adds no additional parameter information beyond the high-level purpose. 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 clearly states the verb 'Add', the resource 'guest group (household)', and the target 'guest list'. It distinguishes this tool from sibling tools like 'add_vendor' and 'invite_guest_to_event' by specifying it adds a household group rather than an individual or vendor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'invite_guest_to_event' for existing guests or 'update_guest_address' for modifications. The description lacks context for the agent to decide between related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/zola-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server