Skip to main content
Glama

Plan a video or voice guestbook

plan_event_guestbook
Read-onlyIdempotent

Use this when the user wants a video guestbook, a voice guestbook, a phone or voicemail guestbook (like a retro guestbook phone) or video messages from guests for a wedding, birthday or any event, without any equipment. Guests scan a QR code and record in their phone's browser: video messages up to 60 seconds, or voice messages on a retro phone screen with an optional selfie. Returns how it works, setup tips for the day and one link that opens the album creation form on Guest Pictures already filled in with the occasion, name and date. Creates and stores nothing. Do not use when the user only wants guests' photos (use plan_guest_photo_album) or a photo booth (use open_photo_booth).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_event_guestbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo"video" for video messages, "voice" for an audio / phone guestbook, "both" if the user wants both or didn't say. Defaults to "both".
languageNo"de" for German-speaking users, "en" otherwise.
occasionNoThe kind of event, e.g. "wedding", "birthday", "anniversary", "graduation", "corporate"; free text is fine.
event_dateNoEvent date as YYYY-MM-DD, only if the user said it.
event_nameNoShort album name as the user would title it, e.g. "Mia & Leo's wedding" (max 60 characters are used). No guest names or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real substance on top: 'Creates and stores nothing', the guest-facing flow (QR scan, recording in phone browser, 60-second video cap, optional selfie on voice), and the exact return payload ('how it works, setup tips for the day and one link that opens the album creation form... already filled in'). That is materially more than the annotations provide.

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

Conciseness4/5

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

Front-loaded with the trigger condition, then the mechanism, then the return value, then the exclusions — a sensible order for an agent scanning for a routing decision. It is a single dense paragraph with some minor redundancy ('without any equipment', 'setup tips for the day'), but no sentence is filler.

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?

There is no output schema, and the description compensates by describing exactly what comes back (how-it-works text, day-of setup tips, one pre-filled album-creation link). Combined with the explicit non-mutation guarantee and the zero-required-parameter design, an agent has everything needed to call this correctly.

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 100%, so the baseline is 3, but the description goes further by tying the input semantics to the user's language ('video guestbook, voice guestbook' maps to the kind enum) and by stating that the returned link is pre-filled with 'the occasion, name and date', which clarifies how occasion, event_name and event_date are used downstream. It does not restate the enum values or date format, which the schema already handles.

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 ('Plan a video or voice guestbook') and immediately enumerates the concrete variants it covers (video, voice, phone/voicemail, retro phone screen, video messages), so an agent can match a user's phrasing without opening the schema. It explicitly names the sibling tools it is not (plan_guest_photo_album, open_photo_booth), making it separable from the rest of the sibling set.

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

Usage Guidelines5/5

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

Gives an explicit positive trigger ('Use this when the user wants a video guestbook, a voice guestbook... for a wedding, birthday or any event') and explicit exclusions with named alternatives ('Do not use when the user only wants guests' photos (use plan_guest_photo_album) or a photo booth (use open_photo_booth)'). Both the when and the when-not are covered with routing instructions.

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