PartyPlan

Server Details

Party budgets, headcount quantities, timelines and checklists. Free.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 18 days
Last Tested: 2026-10-24 19:35
Transport: Streamable HTTP · MCP 2025-11-25
URL
Server Listing: Sahadeva

TDQS

A4.4/5.0

Scored 2026-10-17 06:15 across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose (headcount estimation, budget allocation, supplies checklist, dated timeline), and the descriptions explicitly tell the agent when not to use each tool and which alternative to use. There is no realistic overlap that would cause misselection.

Naming Consistency4/5

Three tools follow a clean party_<noun> pattern (party_budget, party_checklist, party_timeline), but headcount_plan breaks the prefix convention. The deviation is minor and the names remain readable and predictable.

Tool Count5/5

With only four well-scoped tools, each covers a distinct planning dimension and earns its place without redundancy. The count is appropriately lean for a focused party-planning assistant.

Completeness4/5

The set covers the core planning needs: guest-count sizing, budget allocation, supplies/prep checklist, and a dated countdown plan. Minor gaps remain around guest list/RSVP tracking or vendor/invitation management, but these are workable omissions for the stated generative-planning scope.

Available Tools

4 tools

headcount_planHeadcount planA

Read-onlyIdempotent

Inspect

Estimate how many invited guests will attend (adults vs children) and the food, drink, cake, favor and plate quantities to buy, with standard buffers. Use when sizing the shopping list from an invite count. Do NOT use for spending (use party_budget) or a dated to-do plan (use party_timeline).

Name	Required	Description
`invited`	Yes	People invited, whole number 1-1000, e.g. 40
`children_pct`	No	Percent of attendees who are children, 0-100, default 0
`expected_decline_pct`	No	Percent of invitees expected to decline, 0-100, default 15

Output Schema

Name	Required	Description
`note`	Yes	Plain-language explanation of the estimate and buffers
`adults`	Yes	Expected adult attendees
`invited`	Yes	Number of people invited
`children`	Yes	Expected child attendees
`quantities`	Yes	Shopping quantities including buffers
`expected_attendees`	Yes	Expected attendance after declines (rounded up)

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's remaining job is to add context it does not repeat. It discloses that the estimate applies 'standard buffers' and spans adults vs children, which tells the agent the output is buffered and pre-split — useful behavioral context beyond the annotations. It does not describe output shape or how buffers scale, so it stops short of a 5.

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 short sentences: capability first, then usage trigger, then exclusions. Every clause earns its place and the routing information is front-loaded.

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?

An output schema exists, so return values need not be explained, and the three input parameters are fully specified in the schema. The description covers capability, trigger, exclusions and the buffer assumption — everything an agent needs to invoke it 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 coverage is 100% with each parameter fully documented, including ranges and defaults (15% decline). The description only implies the 'invite count' maps to 'invited' and adds no format or interaction detail beyond the schema, so the baseline 3 applies.

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 ('Estimate') and precisely what is estimated (attendee split plus food, drink, cake, favor and plate quantities), and explicitly distinguishes itself from party_budget and party_timeline. An agent can route to this tool without opening any sibling 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 explicit when-to-use ('sizing the shopping list from an invite count') and explicit when-not-to-use with named alternatives for both the spending case (party_budget) and the scheduling case (party_timeline). Nothing is left to inference.

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

party_budgetParty budgetA

Read-onlyIdempotent

Inspect

Allocate a total party budget (USD) across seven categories (venue, food and drink, cake, decorations, entertainment, favors, contingency) by spending style, with per-guest spend and saving tips. Use when deciding what to spend before booking. Do NOT use to estimate attendance or food quantities (use headcount_plan).

Name	Required	Description
`style`	No	Spending style that sets the category percentages: 'budget', 'standard' (default) or 'premium'
`budget`	Yes	Total party budget in USD, positive, e.g. 600
`guests`	Yes	Number of guests, whole number 1-500, e.g. 30

Output Schema

Name	Required	Description
`note`	Yes	Plain-language summary of the allocation
`budget`	Yes	Total budget, rounded to cents
`guests`	Yes	Guest count used
`currency`	Yes	Currency of all amounts, always USD
`allocation`	Yes	Budget split per category; amounts sum to the budget
`per_guest_budget`	Yes	Total budget divided by guests, rounded to cents

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds behavioral context beyond that: it is a pure allocation/calculation that returns per-category splits, per-guest spend, and saving tips. It doesn't address edge cases like style defaults, but for a deterministic calculator that is minor.

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 compact sentences: purpose and output scope first, then positive routing, then the explicit exclusion. No filler and nothing buried.

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?

An output schema exists, so return values need not be explained in prose, yet the description still previews the category breakdown and tips. Combined with full schema coverage and covered safety annotations, the agent has everything needed to invoke it 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%, including the style enum and its meaning and the budget/guests constraints, so the schema does the heavy lifting. The description only names 'spending style' and 'per-guest spend' at a high level, adding little syntax or format meaning beyond the schema. Baseline 3 applies.

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 (allocate a party budget) plus the exact output scope (seven named categories), so the agent knows precisely what it produces. It is clearly distinguishable from headcount_plan, party_checklist, and party_timeline.

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 when-to-use condition ('when deciding what to spend before booking') and an explicit when-not-to-use with the alternative named ('Do NOT use to estimate attendance or food quantities (use headcount_plan)'). This is exactly the routing guidance an agent needs.

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

party_checklistParty checklistA

Read-onlyIdempotent

Inspect

Generate a supplies and prep checklist grouped by area (food and drink, decorations, music and activities, practical, safety) for a home or venue party, with extra items for keywords like pool, bbq, costume, outdoor, kids, alcohol or potluck. Use when preparing what to buy and set up. Do NOT use for a dated plan (use party_timeline).

Name	Required	Description	Default
`venue`	Yes	'home' for a party at home, 'venue' for a hired venue or hall
`extras`	No	Optional keywords that add themed items: pool, bbq, costume, outdoor, kids, alcohol, potluck, e.g. ["bbq","kids"]

Output Schema

Name	Required	Description
`note`	Yes	Summary of venue adjustments and extras applied
`venue`	Yes	Venue type the checklist was built for
`checklist`	Yes	Checklist items grouped by area

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context the annotations do not: the output is grouped by five named areas and keyword extras alter the generated content. It does not describe the return shape, but an output schema exists to carry 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?

Two sentences, zero filler. The generative scope and keyword behavior come first, with the routing exclusion last. Every clause earns its place.

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 generator with an output schema and full annotation coverage, the description supplies everything an agent needs: what it produces, how extras modify it, and how to route against the sibling timeline tool.

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 coverage is 100% and both parameters carry enum/explanations, so the schema does the heavy lifting. The description's mention of keywords like pool, bbq, costume merely restates what the 'extras' schema description already enumerates, adding little beyond the structured fields.

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 ('Generate') and resource ('supplies and prep checklist'), and even names the grouping structure (food and drink, decorations, music and activities, practical, safety). It explicitly distinguishes itself from the sibling party_timeline, so an agent can route without opening a 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 positive trigger ('Use when preparing what to buy and set up') and an explicit exclusion with the named alternative ('Do NOT use for a dated plan (use party_timeline)'). This is the textbook when/when-not/alternative pattern.

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

party_timelineParty timelineA

Read-onlyIdempotent

Inspect

Build a dated countdown plan for a party, with task lists at 6 weeks, 4, 3, 2 and 1 week, 3 days, the day before and the day itself. Use when the date is set and the host needs to know what to do when. Do NOT use for spending (use party_budget) or a categorized supplies list (use party_checklist).

Name	Required	Description
`guests`	No	Optional guest count 1-1000; adds a cake-sizing task at T-14
`event_date`	Yes	Party date YYYY-MM-DD, e.g. 2026-12-20
`event_type`	No	Optional event label added to the T-21 tasks, e.g. 'birthday', 'bbq' or 'kids party'

Output Schema

Name	Required	Description
`note`	Yes	How to read the milestone dates
`event_date`	Yes	Party date YYYY-MM-DD
`milestones`	Yes	Countdown milestones from T-42 days to the day itself

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds the concrete outputs (milestone weeks) but doesn't go beyond annotations on mutation, auth, or failure behavior; with annotations carrying that load, 3 fits.

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: what it builds, when to use, when not to and where to go instead. Front-loaded and zero waste.

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?

Output schema exists, so return values need no explanation. Purpose, outputs, selection guidance and routing to siblings are all present for a 3-param planning tool.

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 coverage is 100% and each parameter has its own description (guests adds a T-14 cake task, event_type labels T-21 tasks). The description adds no parameter detail beyond the schema, so baseline 3 applies.

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 ('Build a dated countdown plan for a party') and enumerates the exact milestones produced, so an agent knows precisely what artifact it gets.

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 both a positive condition ('when the date is set and the host needs to know what to do when') and explicit exclusions routing to party_budget and party_checklist.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesOct 13, 2026

Changedheadcount_plan24 fields changed

changedInput schema / properties / children_pct / description

Previous value: -"Share of attendees who are children, 0-100 (default 0)"New value: +"Percent of attendees who are children, 0-100, default 0"

addedInput schema / properties / children_pct / maximum
```
Added value: +100
```
addedInput schema / properties / children_pct / minimum
```
Added value: +0
```

changedInput schema / properties / expected_decline_pct / description

Previous value: -"Expected share who decline, 0-100 (default 15)"New value: +"Percent of invitees expected to decline, 0-100, default 15"

addedInput schema / properties / expected_decline_pct / maximum
```
Added value: +100
```
addedInput schema / properties / expected_decline_pct / minimum
```
Added value: +0
```

changedInput schema / properties / invited / description

Previous value: -"People invited (1-1000)"New value: +"People invited, whole number 1-1000, e.g. 40"

addedInput schema / properties / invited / maximum
```
Added value: +1000
```
addedInput schema / properties / invited / minimum
```
Added value: +1
```

changedInput schema / properties / invited / type

Previous value: -"number"New value: +"integer"

addedOutput schema / properties / adults

Added value: +{
+  "description": "Expected adult attendees",
+  "type": "integer"
+}

removedOutput schema / properties / cake_slices

Removed value: -{
-  "description": "Number of cake slices needed",
-  "type": "integer"
-}

addedOutput schema / properties / children

Added value: +{
+  "description": "Expected child attendees",
+  "type": "integer"
+}

removedOutput schema / properties / drinks

Removed value: -{
-  "description": "Number of drinks needed",
-  "type": "integer"
-}

removedOutput schema / properties / expected_attendance

Removed value: -{
-  "description": "Estimated number of adults attending",
-  "type": "integer"
-}

addedOutput schema / properties / expected_attendees

Added value: +{
+  "description": "Expected attendance after declines (rounded up)",
+  "type": "integer"
+}

removedOutput schema / properties / expected_children

Removed value: -{
-  "description": "Estimated number of children attending",
-  "type": "integer"
-}

removedOutput schema / properties / favors

Removed value: -{
-  "description": "Number of favors needed",
-  "type": "integer"
-}

addedOutput schema / properties / invited

Added value: +{
+  "description": "Number of people invited",
+  "type": "integer"
+}

removedOutput schema / properties / mains_portions

Removed value: -{
-  "description": "Number of main course portions needed",
-  "type": "integer"
-}

addedOutput schema / properties / note

Added value: +{
+  "description": "Plain-language explanation of the estimate and buffers",
+  "type": "string"
+}

removedOutput schema / properties / plates

Removed value: -{
-  "description": "Number of plates needed",
-  "type": "integer"
-}

addedOutput schema / properties / quantities

Added value: +{
+  "description": "Shopping quantities including buffers",
+  "properties": {
+    "cake_slices": {
+      "description": "Cake slices (20% extra)",
+      "type": "integer"
+    },
+    "drinks": {
+      "description": "Drinks (2.5 per adult, 1.5 per child)",
+      "type": "integer"
+    },
+    "favors": {
+      "description": "Party favors (10% extra)",
+      "type": "integer"
+    },
+    "mains_portions": {
+      "description": "Main-course portions (15% extra per adult, 0.75 per child)",
+      "type": "integer"
+    },
+    "plates": {
+      "description": "Plates (25% extra)",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "mains_portions",
+    "drinks",
+    "cake_slices",
+    "favors",
+    "plates"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "expected_attendance",
-  "expected_children",
-  "mains_portions",
-  "drinks",
-  "cake_slices",
-  "favors",
-  "plates"
-]New value: +[
+  "invited",
+  "expected_attendees",
+  "adults",
+  "children",
+  "quantities",
+  "note"
+]

Changedparty_budget21 fields changed

changedInput schema / properties / budget / description

Previous value: -"Total party budget in USD"New value: +"Total party budget in USD, positive, e.g. 600"

changedInput schema / properties / guests / description

Previous value: -"Number of guests (1-500)"New value: +"Number of guests, whole number 1-500, e.g. 30"

addedInput schema / properties / guests / maximum
```
Added value: +500
```
addedInput schema / properties / guests / minimum
```
Added value: +1
```

changedInput schema / properties / guests / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / style / description

Previous value: -"Spending style, default standard"New value: +"Spending style that sets the category percentages: 'budget', 'standard' (default) or 'premium'"

addedOutput schema / properties / allocation

Added value: +{
+  "description": "Budget split per category; amounts sum to the budget",
+  "items": {
+    "properties": {
+      "amount": {
+        "description": "USD allocated to this category",
+        "type": "number"
+      },
+      "category": {
+        "description": "Budget category key",
+        "enum": [
+          "venue",
+          "food_drink",
+          "cake",
+          "decorations",
+          "entertainment",
+          "favors",
+          "contingency"
+        ],
+        "type": "string"
+      },
+      "percent": {
+        "description": "Percent of the budget for this category",
+        "type": "number"
+      },
+      "tips": {
+        "description": "Saving tip for this category",
+        "type": "string"
+      }
+    },
+    "required": [
+      "category",
+      "percent",
+      "amount",
+      "tips"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / budget

Added value: +{
+  "description": "Total budget, rounded to cents",
+  "type": "number"
+}

removedOutput schema / properties / cake

Removed value: -{
-  "description": "Cost of the cake, in ISO currency code",
-  "properties": {
-    "amount": {
-      "description": "Amount allocated for the cake in USD",
-      "type": "number"
-    },
-    "tip": {
-      "description": "Tip for cake selection",
-      "type": "string"
-    }
-  },
-  "required": [
-    "amount",
-    "tip"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / contingency

Removed value: -{
-  "description": "Amount set aside for unexpected expenses, in ISO currency code",
-  "properties": {
-    "amount": {
-      "description": "Amount allocated for contingency in USD",
-      "type": "number"
-    },
-    "tip": {
-      "description": "Tip for contingency planning",
-      "type": "string"
-    }
-  },
-  "required": [
-    "amount",
-    "tip"
-  ],
-  "type": "object"
-}

addedOutput schema / properties / currency

Added value: +{
+  "description": "Currency of all amounts, always USD",
+  "type": "string"
+}

removedOutput schema / properties / decorations

Removed value: -{
-  "description": "Total cost for decorations, in ISO currency code",
-  "properties": {
-    "amount": {
-      "description": "Amount allocated for decorations in USD",
-      "type": "number"
-    },
-    "tip": {
-      "description": "Tip for decorations selection",
-      "type": "string"
-    }
-  },
-  "required": [
-    "amount",
-    "tip"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / entertainment

Removed value: -{
-  "description": "Cost for entertainment, such as DJ or band, in ISO currency code",
-  "properties": {
-    "amount": {
-      "description": "Amount allocated for entertainment in USD",
-      "type": "number"
-    },
-    "tip": {
-      "description": "Tip for entertainment selection",
-      "type": "string"
-    }
-  },
-  "required": [
-    "amount",
-    "tip"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / favors

Removed value: -{
-  "description": "Total cost for party favors, in ISO currency code",
-  "properties": {
-    "amount": {
-      "description": "Amount allocated for favors in USD",
-      "type": "number"
-    },
-    "tip": {
-      "description": "Tip for favors selection",
-      "type": "string"
-    }
-  },
-  "required": [
-    "amount",
-    "tip"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / food_and_drink

Removed value: -{
-  "description": "Total cost for food and drinks, in ISO currency code",
-  "properties": {
-    "amount": {
-      "description": "Amount allocated for food and drink in USD",
-      "type": "number"
-    },
-    "tip": {
-      "description": "Tip for food and drink selection",
-      "type": "string"
-    }
-  },
-  "required": [
-    "amount",
-    "tip"
-  ],
-  "type": "object"
-}

addedOutput schema / properties / guests

Added value: +{
+  "description": "Guest count used",
+  "type": "integer"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "Plain-language summary of the allocation",
+  "type": "string"
+}

addedOutput schema / properties / per_guest_budget

Added value: +{
+  "description": "Total budget divided by guests, rounded to cents",
+  "type": "number"
+}

removedOutput schema / properties / per_guest_spend

Removed value: -{
-  "description": "Estimated spend per guest in USD",
-  "type": "number"
-}

removedOutput schema / properties / venue

Removed value: -{
-  "description": "Venue costs, including rental and any additional fees, in ISO currency code",
-  "properties": {
-    "amount": {
-      "description": "Amount allocated for the venue in USD",
-      "type": "number"
-    },
-    "tip": {
-      "description": "Tip for venue selection",
-      "type": "string"
-    }
-  },
-  "required": [
-    "amount",
-    "tip"
-  ],
-  "type": "object"
-}

changedOutput schema / required

Previous value: -[
-  "venue",
-  "food_and_drink",
-  "cake",
-  "decorations",
-  "entertainment",
-  "favors",
-  "contingency",
-  "per_guest_spend"
-]New value: +[
+  "currency",
+  "budget",
+  "guests",
+  "per_guest_budget",
+  "allocation",
+  "note"
+]

Changedparty_checklist11 fields changed

changedInput schema / properties / extras / description

Previous value: -"Optional keywords such as 'pool', 'bbq', 'costume', 'outdoor'"New value: +"Optional keywords that add themed items: pool, bbq, costume, outdoor, kids, alcohol, potluck, e.g. [\"bbq\",\"kids\"]"

changedInput schema / properties / venue / description

Previous value: -"Where the party happens"New value: +"'home' for a party at home, 'venue' for a hired venue or hall"

addedOutput schema / properties / checklist

Added value: +{
+  "description": "Checklist items grouped by area",
+  "items": {
+    "properties": {
+      "area": {
+        "description": "Checklist area",
+        "enum": [
+          "food_drink",
+          "decorations",
+          "music_activities",
+          "practical",
+          "safety"
+        ],
+        "type": "string"
+      },
+      "items": {
+        "description": "Items to buy or do for this area",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "area",
+      "items"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / decorations

Removed value: -{
-  "description": "List of decoration items to prepare or purchase.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / food_and_drink

Removed value: -{
-  "description": "List of food and drink items to prepare or purchase.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / music_and_activities

Removed value: -{
-  "description": "List of music and activities to plan.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / note

Added value: +{
+  "description": "Summary of venue adjustments and extras applied",
+  "type": "string"
+}

removedOutput schema / properties / practical_items

Removed value: -{
-  "description": "List of practical items to prepare or purchase.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / safety_notes

Removed value: -{
-  "description": "List of safety notes to consider.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / venue

Added value: +{
+  "description": "Venue type the checklist was built for",
+  "enum": [
+    "home",
+    "venue"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "food_and_drink",
-  "decorations",
-  "music_and_activities",
-  "practical_items",
-  "safety_notes"
-]New value: +[
+  "venue",
+  "checklist",
+  "note"
+]

Changedparty_timeline13 fields changed

changedInput schema / properties / event_date / description

Previous value: -"Party date in YYYY-MM-DD format"New value: +"Party date YYYY-MM-DD, e.g. 2026-12-20"

changedInput schema / properties / event_type / description

Previous value: -"Optional event label, e.g. 'birthday', 'bbq' or 'kids party'"New value: +"Optional event label added to the T-21 tasks, e.g. 'birthday', 'bbq' or 'kids party'"

changedInput schema / properties / guests / description

Previous value: -"Optional guest count for cake sizing"New value: +"Optional guest count 1-1000; adds a cake-sizing task at T-14"

addedInput schema / properties / guests / maximum
```
Added value: +1000
```
addedInput schema / properties / guests / minimum
```
Added value: +1
```

changedInput schema / properties / guests / type

Previous value: -"number"New value: +"integer"

changedOutput schema / properties / event_date / description

Previous value: -"The date of the party in YYYY-MM-DD format."New value: +"Party date YYYY-MM-DD"

removedOutput schema / properties / event_type

Removed value: -{
-  "description": "The type of event, e.g., 'birthday', 'bbq', or 'kids party'.",
-  "type": "string"
-}

removedOutput schema / properties / guests

Removed value: -{
-  "description": "The number of guests attending the party.",
-  "type": "number"
-}

addedOutput schema / properties / milestones

Added value: +{
+  "description": "Countdown milestones from T-42 days to the day itself",
+  "items": {
+    "properties": {
+      "date": {
+        "description": "Calendar date YYYY-MM-DD to finish these tasks by",
+        "type": "string"
+      },
+      "tasks": {
+        "description": "Tasks for this milestone",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "when": {
+        "description": "Offset label, e.g. 'T-14 days'",
+        "type": "string"
+      }
+    },
+    "required": [
+      "when",
+      "date",
+      "tasks"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "How to read the milestone dates",
+  "type": "string"
+}

removedOutput schema / properties / timeline

Removed value: -{
-  "description": "A list of milestones and tasks leading up to the party.",
-  "items": {
-    "properties": {
-      "days_until": {
-        "description": "The number of days until the party for this milestone.",
-        "type": "number"
-      },
-      "tasks": {
-        "description": "A list of tasks to complete for this milestone.",
-        "properties": {
-          "cake": {
-            "description": "Tasks related to the cake.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "confirmations": {
-            "description": "Tasks related to confirmations.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "decorations": {
-            "description": "Tasks related to decorations.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "invitations": {
-            "description": "Tasks related to invitations.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "menu": {
-            "description": "Tasks related to the menu.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "run_sheet": {
-            "description": "Tasks for the day-of run sheet.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "setup": {
-            "description": "Tasks related to setup.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "venue": {
-            "description": "Tasks related to the venue.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "type": "object"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / required

Added value: +[
+  "event_date",
+  "milestones",
+  "note"
+]

1 tool updateOct 6, 2026

Changedparty_budget7 fields changed

addedOutput schema / properties / cake / description

Added value: +"Cost of the cake, in ISO currency code"

addedOutput schema / properties / contingency / description

Added value: +"Amount set aside for unexpected expenses, in ISO currency code"

addedOutput schema / properties / decorations / description

Added value: +"Total cost for decorations, in ISO currency code"

addedOutput schema / properties / entertainment / description

Added value: +"Cost for entertainment, such as DJ or band, in ISO currency code"

addedOutput schema / properties / favors / description

Added value: +"Total cost for party favors, in ISO currency code"

addedOutput schema / properties / food_and_drink / description

Added value: +"Total cost for food and drinks, in ISO currency code"

addedOutput schema / properties / venue / description

Added value: +"Venue costs, including rental and any additional fees, in ISO currency code"

4 tool updatesOct 6, 2026

Changedheadcount_plan1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cake_slices": {
+      "description": "Number of cake slices needed",
+      "type": "integer"
+    },
+    "drinks": {
+      "description": "Number of drinks needed",
+      "type": "integer"
+    },
+    "expected_attendance": {
+      "description": "Estimated number of adults attending",
+      "type": "integer"
+    },
+    "expected_children": {
+      "description": "Estimated number of children attending",
+      "type": "integer"
+    },
+    "favors": {
+      "description": "Number of favors needed",
+      "type": "integer"
+    },
+    "mains_portions": {
+      "description": "Number of main course portions needed",
+      "type": "integer"
+    },
+    "plates": {
+      "description": "Number of plates needed",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "expected_attendance",
+    "expected_children",
+    "mains_portions",
+    "drinks",
+    "cake_slices",
+    "favors",
+    "plates"
+  ],
+  "type": "object"
+}

Changedparty_budget1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cake": {
+      "properties": {
+        "amount": {
+          "description": "Amount allocated for the cake in USD",
+          "type": "number"
+        },
+        "tip": {
+          "description": "Tip for cake selection",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "tip"
+      ],
+      "type": "object"
+    },
+    "contingency": {
+      "properties": {
+        "amount": {
+          "description": "Amount allocated for contingency in USD",
+          "type": "number"
+        },
+        "tip": {
+          "description": "Tip for contingency planning",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "tip"
+      ],
+      "type": "object"
+    },
+    "decorations": {
+      "properties": {
+        "amount": {
+          "description": "Amount allocated for decorations in USD",
+          "type": "number"
+        },
+        "tip": {
+          "description": "Tip for decorations selection",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "tip"
+      ],
+      "type": "object"
+    },
+    "entertainment": {
+      "properties": {
+        "amount": {
+          "description": "Amount allocated for entertainment in USD",
+          "type": "number"
+        },
+        "tip": {
+          "description": "Tip for entertainment selection",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "tip"
+      ],
+      "type": "object"
+    },
+    "favors": {
+      "properties": {
+        "amount": {
+          "description": "Amount allocated for favors in USD",
+          "type": "number"
+        },
+        "tip": {
+          "description": "Tip for favors selection",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "tip"
+      ],
+      "type": "object"
+    },
+    "food_and_drink": {
+      "properties": {
+        "amount": {
+          "description": "Amount allocated for food and drink in USD",
+          "type": "number"
+        },
+        "tip": {
+          "description": "Tip for food and drink selection",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "tip"
+      ],
+      "type": "object"
+    },
+    "per_guest_spend": {
+      "description": "Estimated spend per guest in USD",
+      "type": "number"
+    },
+    "venue": {
+      "properties": {
+        "amount": {
+          "description": "Amount allocated for the venue in USD",
+          "type": "number"
+        },
+        "tip": {
+          "description": "Tip for venue selection",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "tip"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "venue",
+    "food_and_drink",
+    "cake",
+    "decorations",
+    "entertainment",
+    "favors",
+    "contingency",
+    "per_guest_spend"
+  ],
+  "type": "object"
+}

Changedparty_checklist1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "decorations": {
+      "description": "List of decoration items to prepare or purchase.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "food_and_drink": {
+      "description": "List of food and drink items to prepare or purchase.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "music_and_activities": {
+      "description": "List of music and activities to plan.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "practical_items": {
+      "description": "List of practical items to prepare or purchase.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "safety_notes": {
+      "description": "List of safety notes to consider.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "food_and_drink",
+    "decorations",
+    "music_and_activities",
+    "practical_items",
+    "safety_notes"
+  ],
+  "type": "object"
+}

Changedparty_timeline1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "event_date": {
+      "description": "The date of the party in YYYY-MM-DD format.",
+      "type": "string"
+    },
+    "event_type": {
+      "description": "The type of event, e.g., 'birthday', 'bbq', or 'kids party'.",
+      "type": "string"
+    },
+    "guests": {
+      "description": "The number of guests attending the party.",
+      "type": "number"
+    },
+    "timeline": {
+      "description": "A list of milestones and tasks leading up to the party.",
+      "items": {
+        "properties": {
+          "days_until": {
+            "description": "The number of days until the party for this milestone.",
+            "type": "number"
+          },
+          "tasks": {
+            "description": "A list of tasks to complete for this milestone.",
+            "properties": {
+              "cake": {
+                "description": "Tasks related to the cake.",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "confirmations": {
+                "description": "Tasks related to confirmations.",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "decorations": {
+                "description": "Tasks related to decorations.",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "invitations": {
+                "description": "Tasks related to invitations.",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "menu": {
+                "description": "Tasks related to the menu.",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "run_sheet": {
+                "description": "Tasks for the day-of run sheet.",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "setup": {
+                "description": "Tasks related to setup.",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "venue": {
+                "description": "Tasks related to the venue.",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

4 tool updatesOct 4, 2026
- First observedheadcount_plan
- First observedparty_budget
- First observedparty_checklist
- First observedparty_timeline

Related MCP Connectors

Partiful by Cotlet A
dev.cotlet
Invites, guest lists and text blasts for your events.
Communication Calendar Management
3111
https://cotlet.dev/mcp/v1/partiful
lesgooo.fun B
fun.lesgooo
Free no-signup group planner: dates, RSVPs, place votes, shared checklist and split costs.
Calendar Management Project Management Workplace & Productivity
231
https://lesgooo.fun/mcp
Lemonvite AOAuth
com.lemonvite
Create, design and send event invitations, manage guest lists, and track RSVPs.
Content Management Systems Design Tools
181
https://www.lemonvite.com/api/mcp
Aisle A
wedding.aisle
Find wedding venues and vendors, estimate costs, and manage guests, events and wedding details.
Location Services Finance Project Management
441
https://aisle.wedding/api/claude/mcp

Related MCP Servers

Wedding Manager MCP
Project Management Finance Communication
choijay0310-spec
F
license
Not graded
quality
D
maintenance
Enables users to manage wedding preparation tasks including timeline generation, budget review, vendor quote comparison, role assignment briefs, and drafting messages for family, vendors, and friends.
Updated 4 months ago (2026-06-19 08:29 UTC)
-
aisle-wedding-mcp
Travel & Transportation E-commerce & Retail
Nunya-design
F
license
Not graded
quality
C
maintenance
Search destination wedding venues and vendors worldwide with Aisle. 10 tools for AI-assisted wedding planning: Venue Search: Find wedding venues by country, type (villa, beach, castle, resort), capacity, and budget. Covers 20+ countries. Vendor Search: Browse wedding photographers, florists, planners, DJs, caterers, and 10 more categories by location and price range. Budget Estimator: Get a detai
Updated 9 days ago (2026-10-16 06:04 UTC)
-
Eventflare MCP
Search Location Services
mluckx
A
license
A
quality
D
maintenance
Search 8,000+ corporate event venues across 40+ cities. Tools for venue search by capacity/category, pricing guides, expert advice articles, and inquiry handoff. Read-only, PII-redacted, UTM-attributed.
Updated 6 months ago (2026-05-05 18:39 UTC)
7
5 npm
MIT
invitas MCP connectorofficial
Calendar Management Communication Workplace & Productivity
invitas-co
A
license
Not graded
quality
C
maintenance
Enables hosts and developers to create and manage invitas invitations and guest lists from AI assistants, including editing invitation text, sharing personal guest links, recording attendance confirmations, arranging tables, and preparing reminders. Connects over Streamable HTTP with OAuth 2.1 and scoped read/write permissions for events, guests, and seating.
Updated 2 days ago (2026-10-23 04:42 UTC)
CC BY-4.0