Skip to main content
Glama

Get Wedding Day Timeline Template

zola_get_wedding_day_timeline_template
Read-only

Use this when the user asks for an example schedule of a wedding day. Zola's general wedding day timeline template, from the guest arrival to the farewell, moved to the given ceremony time. The example day starts 1 hour before the ceremony and ends 5 hours after it, so the ceremony time must be from 07:00 to 19:00. Do not use for the times of the couple's own events: use zola_get_my_wedding_events.

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": {
      "ceremony_time": "<ceremony_time>"
    },
    "name": "zola_get_wedding_day_timeline_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
ceremony_timeYesCeremony time, HH:MM, 24-hour, from 07:00 to 19:00

Output Schema

NameRequiredDescriptionDefault
eventsYesThe events of the wedding day, in time order
sourceYesThe Zola article that gives these values
ceremony_timeYesCeremony time, HH:MM, 24-hour

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: the generated day starts 1 hour before the ceremony and ends 5 hours after, which explains why the caller is constrained to 07:00–19:00. It stops short of describing the returned schedule's granularity, though the output schema exists to cover that.

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: trigger first, then what the template is, then the constraint and its reason, then the exclusion. The bounds repetition is justified because it is accompanied by the explanation of why the bounds exist.

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 single-required-parameter, read-only template tool this covers trigger, scope, constraint rationale, and the disambiguation an agent most needs. Return values are handled by the output schema, so nothing material is left unsaid.

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% and the HH:MM 24-hour format and bounds are already in the schema, so the baseline would be 3. The description earns more by supplying the rationale for the 07:00–19:00 window (1 hour before start, 5 hours after end), which lets the agent judge valid inputs rather than merely pattern-match them.

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+resource: a general wedding day timeline template spanning guest arrival to farewell, anchored to the supplied ceremony time. It also names the sibling it must not be confused with (zola_get_my_wedding_events), so an agent can separate the two without opening either schema.

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 trigger ('when the user asks for an example schedule of a wedding day') and an explicit exclusion with the correct alternative ('Do not use for the times of the couple's own events: use zola_get_my_wedding_events'). This is the when/when-not/alternative pattern at full strength.

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