Skip to main content
Glama

WhoIsBringing Potluck & Event Signups

create_event_checklist

Create a new collaborative event checklist (for BBQs, camping, picnics, potlucks, and dinners) with categorized items, quantities, date, location, and host name. Returns a live shareable URL and invite copy.

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": {
      "title": "<title>",
      "host_name": "<host_name>"
    },
    "name": "create_event_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoList of supply and food items needed
titleYesEvent title (e.g. "Saturday BBQ Cookout" or "Family Lake Picnic")
locationNoOptional venue, address, or park landmark
templateNoPreset template category
host_nameYesHost or organizer display name
event_dateNoOptional date and time (e.g. "2026-09-05T15:00")
descriptionNoOptional event notes or instructions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / title / description
      Previous value: -"Event title (e.g. \"Grand Saturday Braai & Rugby\" or \"Family Lake Picnic\")"New value: +"Event title (e.g. \"Saturday BBQ Cookout\" or \"Family Lake Picnic\")"
  2. Changed4 schema fields changed
    • changedInput schema / properties / host_name / description
      Previous value: -"Host or organizer display name [Required: non-empty valid value must be supplied]."New value: +"Host or organizer display name"
    • changedInput schema / properties / items / description
      Previous value: -"List of supply and food items needed [Optional: omit to use server default filter]."New value: +"List of supply and food items needed"
    • changedInput schema / properties / template / description
      Previous value: -"Preset template category [Optional: omit to use server default filter]."New value: +"Preset template category"
    • changedInput schema / properties / title / description
      Previous value: -"Event title (e.g. \"Grand Saturday Braai & Rugby\" or \"Family Lake Picnic\") [Required: non-empty valid value must be supplied]."New value: +"Event title (e.g. \"Grand Saturday Braai & Rugby\" or \"Family Lake Picnic\")"
  3. Changed4 schema fields changed
    • changedInput schema / properties / host_name / description
      Previous value: -"Host or organizer display name"New value: +"Host or organizer display name [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / items / description
      Previous value: -"List of supply and food items needed"New value: +"List of supply and food items needed [Optional: omit to use server default filter]."
    • changedInput schema / properties / template / description
      Previous value: -"Preset template category"New value: +"Preset template category [Optional: omit to use server default filter]."
    • changedInput schema / properties / title / description
      Previous value: -"Event title (e.g. \"Grand Saturday Braai & Rugby\" or \"Family Lake Picnic\")"New value: +"Event title (e.g. \"Grand Saturday Braai & Rugby\" or \"Family Lake Picnic\") [Required: non-empty valid value must be supplied]."
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key outcome: a live shareable URL and invite copy, with 'collaborative' and 'live' hinting that the checklist becomes mutable shared state. It says nothing about permissions, ownership, whether the creator is auto-assigned as host, or what happens on duplicate titles.

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 compact sentences with the action front-loaded and no filler; the parenthetical example list and the return-value sentence both add information rather than padding.

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?

For a flat 7-parameter creation tool with no output schema and no annotations, the description covers purpose, payload, and result, which is nearly everything an agent needs. The remaining gap is the template/items interaction and sharing permissions, which matter for correct invocation in edge cases.

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 explains every field and the template enum values. The description only restates the field list, adding no detail on how template interacts with items (e.g. whether it pre-populates suggested items) or what happens when template is 'none'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a new collaborative event checklist') and enumerates the payload (categorized items, quantities, date, location, host name) plus the return value. It never names a sibling, so the boundary with get_event_checklist or add_checklist_items is left to be inferred from the verb alone.

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 parenthetical use cases (BBQs, camping, picnics, potlucks, dinners) imply the intended scenario, making usage reasonably clear. There is no when-not-to-use guidance and no pointer telling the agent to use add_checklist_items for appending to an existing checklist rather than creating a new one.

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