Skip to main content
Glama
Sign In

checklists

by com.wildernesstimes
OverviewDiscussionsAdmin

Build a custom packing list

build_checklist
Read-onlyIdempotent

Build a customised packing list from a Wilderness Times checklist: start from an activity, optionally keep only certain categories, drop items that do not apply, and add your own. Returns the tailored list plus buying-guide links for whatever survived. Suited to a list shaped to one specific trip rather than the full standard one.

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": {
      "activity": "<activity>"
    },
    "name": "build_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNoOptional. Extra items to append under a 'Your additions' category.
excludeNoOptional. Item names to leave out (matched loosely — 'hammock' drops 'Hammock').
activityYesBase activity. One of: camping, backpacking, hiking, winter-camping, cabin-camping, couples-camping, kayak-camping, motorcycle-camping, toddler-camping, beach-camping, fishing, snowboarding.
categoriesNoOptional. Keep only these categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / activity / description
      Previous value: -"Base activity. One of: camping, backpacking, hiking, winter-camping, cabin-camping, couples-camping, kayak-camping, motorcycle-camping, toddler-camping, fishing, snowboarding."New value: +"Base activity. One of: camping, backpacking, hiking, winter-camping, cabin-camping, couples-camping, kayak-camping, motorcycle-camping, toddler-camping, beach-camping, fishing, snowboarding."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful behavioral detail: the transformation steps and that the result includes the tailored list plus buying-guide links. It does not cover error behavior for invalid activities, but the schema enumerates allowed values.

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?

Front-loads the core purpose, then packs the transformation steps, return content, and usage contrast into two efficient sentences with no filler. Every clause contributes to correct invocation.

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?

Given four parameters, full schema descriptions, and annotations, the description is complete enough: it explains inputs, transformation behavior, output content, and the intended use case. No output schema exists, and the description covers what is returned.

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%, so every parameter is already documented in structured data. The description maps each operation to a parameter (activity base, categories filter, exclude drops, add appends) but adds no format or matching details beyond the schema, so the baseline 3 is appropriate.

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 and resource ('Build a customised packing list from a Wilderness Times checklist') and clarifies the tailored scope as opposed to the full standard list. An agent can tell this apart from a standard checklist-fetching sibling without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames when this tool is appropriate: for a list shaped to one specific trip rather than the full standard one. It implies the alternative and the condition but does not explicitly name the sibling (e.g. get_checklist) or give imperative routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All checklists toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources