Skip to main content
Glama

Generate Packing List

generate_packing_list
Idempotent

Create a weather- and activity-aware packing checklist for a trip, grouped into sections and saved as a pinned checklist note. Never changes an existing list: if one already exists it is returned unchanged; use packing_list_regenerate to replace it. Requires the trip to have a destination or at least one itinerary item. Provide the trip_id from trips_list. For one list per person, pass people (max 6). Tineo builds the list on its servers with its AI model provider, sending the trip's title, dates, destinations, itinerary items, weather forecast, any context_notes, and each person's age band and notes (never their name).

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": {
      "trip_id": "<trip_id>"
    },
    "name": "generate_packing_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
peopleNoOptional. One personalized list per person (max 6), titled with the person's name.
trip_idYesTineo trip ID (from trips_list).
context_notesNoOptional packing-relevant details the user asked to include, such as planned activities or special gear. Pass only what the user wants reflected in the list. Never include health conditions, medical details or other sensitive personal information.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which already declare idempotent, non-destructive, open-world), the description explains the actual idempotency behavior — an existing list is returned unchanged rather than overwritten — and the prerequisite conditions. It also discloses the server-side AI generation step and exactly which trip data leaves the system versus what is withheld (person names, health details), which is genuine behavioral context an agent cannot get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Sentences are dense but each carries a distinct fact — behavior, alternative, precondition, parameter guidance, data-flow disclosure — and the most important constraint (never mutates) is front-loaded. Minor cost: the privacy detail is repeated for both people and context_notes, and the final server-side sentence is long.

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?

There is no output schema, yet the description says what is produced (sectioned pinned checklist note, one per person) and under what conditions. Combined with prerequisites, limits, and data-sharing details, an agent has everything needed to invoke it correctly and to warn users about what is sent to the AI provider.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining data-handling semantics for parameters — the person 'name' is only a list title and never sent to the model provider, and 'people' yields one list per person up to 6. It does not add much on trip_id or context_notes beyond what the schema already documents.

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 opens with a specific verb and resource: 'Create a weather- and activity-aware packing checklist for a trip, grouped into sections and saved as a pinned checklist note.' It also explicitly distinguishes itself from the sibling packing_list_regenerate, so an agent can route correctly without opening either 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?

It states the key exclusion ('Never changes an existing list: if one already exists it is returned unchanged'), names the alternative tool for replacement (packing_list_regenerate), and gives the precondition ('Requires the trip to have a destination or at least one itinerary item'). It even points to the source of the ID ('Provide the trip_id from trips_list'), leaving nothing to inference.

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