Skip to main content
Glama

Add moment

add-moment

Adds a moment of the wedding day that guests can be invited to (e.g. "Walking dinner"). Without a date it takes the wedding date, without a location the venue. A dinner gets fixed seats (a seating plan) unless seated is false. Invite guests to it with update-guest.

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": {
      "name": "<name>"
    },
    "name": "add-moment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD.
nameYesHow the couple calls it, e.g. "Ceremonie in de tuin".
typeNoburgerlijk (civil ceremony at the town hall), ceremonie, receptie, diner, feest (party) or andere.
notesNoPrivate notes of the couple.
seatedNoFixed seats, so the moment has a seating plan. Turning it off keeps the tables.
name_enNoEnglish name for guests reading the site in English.
visibleNoShown to guests on the website, the RSVP page and in mails. A hidden moment can still have invitations.
capacityNoMaximum number of people.
end_timeNoHH:MM; at or before the start means the next day.
locationNo
start_timeNoHH:MM, e.g. "19:00". Needs a date.
uninvited_noteNoWhat guests who are not invited to this moment read at its time, e.g. "Bring something to eat".
uninvited_note_enNoThe same in English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, closed-world. The description adds real behavioral context beyond that: omitted date falls back to the wedding date, omitted location falls back to the venue, and a dinner gets a seating plan by default unless seated is false. It stops short of noting side effects such as whether invitations or notifications are triggered on creation.

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?

Three tight sentences plus a routing pointer, front-loaded with the purpose then the defaults. No filler, and every clause carries either identifying or behavioral information.

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?

For a 13-parameter create tool with 92% schema coverage and no output schema, the description supplies exactly what the schema cannot: default inheritance and the seating-plan consequence of type. Annotations cover the safety profile, so nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 92%, so the baseline is 3, but the description adds genuine meaning the schema lacks: default-inheritance rules for date (wedding date) and location (venue), which are undocumented in the schema for location. The seated default behavior is reinforced at the tool level, giving the agent decision-relevant context rather than restating field docs.

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 ("Adds a moment of the wedding day") with a concrete example ("Walking dinner") and clarifies the resource further as something guests can be invited to. The creation intent cleanly separates it from update-moment/delete-moment/list-moments siblings without needing to name them.

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?

Makes clear this is the creation path for a wedding-day moment and routes a follow-up action explicitly ("Invite guests to it with update-guest"). It does not state when not to use it, e.g. to modify an existing moment via update-moment, but the create context is unambiguous.

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