PartyPlan

Party checklist

party_checklist

Read-onlyIdempotent

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).

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 13, 2026

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"
+]

Changed1 schema field changedOct 6, 2026

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"
+}

First observedOct 4, 2026

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.

All PartyPlan tools Inspect

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.