Skip to main content
Glama

WhoIsBringing Potluck & Event Signups

add_checklist_items

Append additional food, drinks, or supply items to an existing event checklist.

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": {
      "event_id": "<event_id>",
      "items": "<items>"
    },
    "name": "add_checklist_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesArray of items to append
event_idYesThe 8-character event ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / items / description
      Added value: +"Array of items to append"
  2. Changed2 schema fields changed
    • changedInput schema / properties / event_id / description
      Previous value: -"The 8-character event ID [Required: non-empty valid value must be supplied]."New value: +"The 8-character event ID"
    • removedInput schema / properties / items / description
      Removed value: -"Parameter 'items' (array). [Required: non-empty valid value must be supplied]."
  3. Changed2 schema fields changed
    • changedInput schema / properties / event_id / description
      Previous value: -"The 8-character event ID"New value: +"The 8-character event ID [Required: non-empty valid value must be supplied]."
    • addedInput schema / properties / items / description
      Added value: +"Parameter 'items' (array). [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?

No annotations are provided, so the description carries full burden. It does disclose that the operation is additive ('append additional ... items') against an existing resource, but says nothing about duplicate handling, idempotency, required permissions, or what happens on failure — meaningful gaps for a mutation tool.

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?

A single front-loaded sentence with no filler; the verb, scope, and target resource all appear immediately.

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 two-parameter tool with a fully described schema and no output schema, the description covers purpose, target, and additive behavior adequately. It would be stronger with a note on duplicate items and the state of the existing checklist after appending.

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 both parameters and the nested item fields are already documented in the schema. The description adds only domain color ('food, drinks, or supply items') and no new semantics for event_id or the item object.

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 ('Append ... items to an existing event checklist') and scopes the target as an existing checklist, which implicitly separates it from creation/read siblings like create_event_checklist and get_event_checklist. It doesn't explicitly name an alternative, so it stops short of a 5.

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 phrase 'existing event checklist' implies a prerequisite (the checklist must already exist) and 'append additional' implies use when adding to, not replacing, a list. There is no explicit when-to-use/when-not guidance or named alternative for creating a new checklist.

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