Skip to main content
Glama

Get Wedding Planning Timeline Template

zola_get_planning_timeline_template
Read-only

Use this when the user asks what a couple usually does by when, for a wedding date. Zola's general planning timeline template, dated: the planning milestones for a wedding date and a wedding format (traditional, small, destination, elopement, or courthouse). Each milestone has a start date and a due date, counted back from the wedding date, and a status relative to today: late, now, later, or after the wedding. A milestone that applies only in some cases, for example a honeymoon, is marked optional. Do not use for the couple's own tasks or progress: use zola_get_my_checklist or zola_get_my_planning_overview.

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": {
      "wedding_date": "<wedding_date>"
    },
    "name": "zola_get_planning_timeline_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoWedding format. The default is traditional.traditional
wedding_dateYesWedding date, YYYY-MM-DD. From today to 5 years after today.

Output Schema

NameRequiredDescriptionDefault
todayYesThe day that the statuses are relative to, YYYY-MM-DD (UTC)
formatYesWedding format of the timeline
milestonesYesThe milestones of the format, late and now first, then by due date
wedding_dateYesWedding date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already mark this as a safe read-only, non-destructive, closed-world operation. The description adds substantial behavior beyond that: milestones have start and due dates counted back from the wedding date, statuses relative to today, and optional markers for conditional milestones such as a honeymoon.

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 front-loaded with the use case, then explains the template structure, then gives the exclusion and alternatives. Every sentence contributes useful selection or interpretation guidance, with no wasted wording.

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 two-parameter read-only template tool with an output schema, the description covers the selection context, output semantics such as status and optional milestones, and the relevant alternative tools. Nothing an agent needs in order to choose and invoke it correctly is missing.

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. The description adds meaning by explaining that milestones are counted back from the wedding date and that the template depends on the wedding format, though it mostly repeats the schema's enum values rather than adding new syntax or constraints.

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 states a specific resource and scope: Zola's general wedding planning timeline template with dated milestones for a wedding date and format. It explicitly distinguishes this from the couple's own tasks and progress, so an agent can identify the tool without guessing.

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?

It gives an explicit trigger: use when the user asks what a couple usually does by when. It also states the exclusion and names the alternatives, zola_get_my_checklist and zola_get_my_planning_overview, for the couple's own tasks or progress.

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