Skip to main content
Glama

Generate packing checklist

generate_packing_checklist
Read-onlyIdempotent

Use this when the user supplies packing items and wants a checkable packing checklist, quantity totals, duplicate merging, and A4 or Letter PDF and CSV downloads. Same-name duplicates in the same category merge case-insensitively; quantities sum. Mixed packed duplicate states reset that line to unchecked. A packed line means all its units. Does not recommend items, give travel or health advice, track luggage weight, or sync progress. PDF simplifies accents and replaces unsupported characters. Up to 40 input lines within a 2,800-byte payload.

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

Input Schema

NameRequiredDescriptionDefault
itemsYesOnly explicit supplied packing items, e.g. [{name:"socks",category:"Clothing",quantity:3}].
paperNoPDF page size, e.g. A4 (default) or Letter.
titleNoOptional checklist title, e.g. Weekend bag.

Output Schema

NameRequiredDescriptionDefault
paperYes
titleYes
warningsYes
downloadsYes
line_countYes
input_countYes
category_countYes
total_quantityYes
duplicate_countYes
packed_quantityYes
remaining_quantityYes

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 (readOnly, idempotent, non-destructive), the description discloses non-obvious behavior: case-insensitive merging of same-name items within a category, quantity summing, and that mixed packed states reset the line to unchecked. It also flags real constraints an agent must respect — 40 input lines, a 2,800-byte payload cap, and PDF character/accent simplification.

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?

Content is front-loaded with the trigger and deliverable, and every sentence carries real information. It is a single dense block of clauses, though — the merge/state rules could be split more cleanly for scanning, which costs a point.

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 tool with an output schema, full schema coverage, and clear annotations, the description covers the remaining gaps an agent needs: merge rules, packed-state semantics, hard size limits, character handling, and explicit scope exclusions. Nothing required for correct invocation is missing.

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, and the description adds genuine meaning on top: it explains the merge semantics that govern how multiple `items` entries collapse, and notes the 2,800-byte payload limit that the schema itself does not state. It does not elaborate on `paper` or `title` beyond the schema, which keeps it below a 5.

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 states a specific verb and resource — generating a checkable packing checklist from user-supplied items — and enumerates the concrete outputs (quantity totals, duplicate merging, A4/Letter PDF and CSV downloads). An agent knows exactly what the tool produces without opening the 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 opens with an explicit trigger condition ('Use this when the user supplies packing items and wants...') and follows with an explicit exclusion list: no item recommendations, no travel or health advice, no luggage weight tracking, no progress sync. Both sides of the use/do-not-use boundary are stated.

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