Skip to main content
Glama

Wedyesday — wedding planning

by com.wedyesday.mcp
OverviewDiscussionsAdmin

Build a wedding plan

build_wedding_plan
Read-onlyIdempotent

Build a personalised wedding plan: a month-by-month checklist with real due dates, a budget split for the couple's region, and how their budget compares to typical local spend. This is the same planning engine as the Wedyesday website, so nothing here is invented. Nothing is saved and no account is needed — follow up with create_wedyesday_workspace_link when the couple wants to keep it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoTotal budget in whole currency units (e.g. 45000). Omit if the couple does not have one yet — a regional typical figure is used instead.
regionNoRegion slug from list_wedding_markets, e.g. "melbourne" or "london". Drives the budget split and legal steps.
seasonNoRequired when dateMode is "season".
countryNoISO country code: AU, US, GB, NZ or IN. Pass the couple's country — the legal steps and budget split depend on it; defaults to AU when omitted.
dateModeNo"fixed" when the date is set, "season" when only a season and year are known, "undecided" otherwise.
locationNoWhere the wedding is, e.g. "Melbourne, VIC" or "London".
eventDateNoWedding date as YYYY-MM-DD. Required when dateMode is "fixed".
guestCountYesExpected number of guests, 2-2000.
partnerOneNoFirst partner's first name.
partnerTwoNoSecond partner's first name.
prioritiesNoUp to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling.
seasonYearNoYear for the chosen season.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO country code: AU, US, GB, NZ or IN. Defaults to AU."New value: +"ISO country code: AU, US, GB, NZ or IN. Pass the couple's country — the legal steps and budget split depend on it; defaults to AU when omitted."
    • changedInput schema / properties / location / description
      Previous value: -"Where the wedding is, e.g. \"Melbourne, VIC\"."New value: +"Where the wedding is, e.g. \"Melbourne, VIC\" or \"London\"."
    • changedInput schema / properties / region / description
      Previous value: -"Region slug from list_wedding_markets, e.g. \"melbourne\". Drives the budget split and legal steps."New value: +"Region slug from list_wedding_markets, e.g. \"melbourne\" or \"london\". Drives the budget split and legal steps."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds that nothing is saved and no account is needed, which is specific behavioral context beyond the safety flags. It also assures authenticity ('nothing here is invented'), giving agents confidence in the data. It doesn't contradict the annotations.

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 two sentences with no filler. The first sentence front-loads the core purpose and output components, and the second adds essential context about persistence and authenticity. Every sentence earns its place.

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

Completeness4/5

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

With no output schema, the description must convey the result shape, which it does by specifying the checklist, budget split, and comparison. It also mentions the follow-up tool and the no-save behavior. It could be more explicit about legal steps or the exact output format, but it's fairly complete for an agent to invoke correctly.

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 description coverage is 100%, so the schema already documents all parameters. The description mentions that the budget and region drive the split and comparison, adding slight context, but it doesn't add substantial meaning beyond what the schema provides. The baseline of 3 is appropriate given the high schema coverage.

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 tool's function: it builds a personalised wedding plan with a month-by-month checklist, budget split, and comparison to local spend. It distinguishes itself from siblings like get_wedding_cost_guide by specifying the comprehensive plan output, and it notes it's the same engine as the website.

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

Usage Guidelines3/5

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

The description implies when to use the tool (when the couple wants a full plan) and explicitly mentions a follow-up tool (create_wedyesday_workspace_link) for saving, but it does not explicitly contrast with other siblings like get_wedding_cost_guide or get_my_wedding_budget. It provides context but lacks clear exclusions or alternative selection criteria.

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

All Wedyesday — wedding planning toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources