Skip to main content
Glama
Sign In

checklists

by com.wildernesstimes
OverviewDiscussionsAdmin

Get a packing checklist

get_checklist
Read-onlyIdempotent

Get a full Wilderness Times packing checklist for one activity, organised by category, with links to the buying guides that help choose specific gear. Answers what to pack for a trip. Accepts natural phrasing ('car camping', 'camping with kids') as well as exact activity ids.

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": "get_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityYesActivity to fetch. One of: camping, backpacking, hiking, winter-camping, cabin-camping, couples-camping, kayak-camping, motorcycle-camping, toddler-camping, beach-camping, fishing, snowboarding. Common phrasings are also accepted.
categoriesNoOptional. Only return these categories (matched loosely). Use to narrow a 100+ item list when the user only wants, say, the cooking or sleeping section.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/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, so the safety profile is free. The description adds real value beyond that by describing the return shape (full checklist, categorised, with links to buying guides) in the absence of an output schema.

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?

Three short sentences, front-loaded with what the tool returns, then the use case, then the input tolerance. No filler and no repetition.

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?

With rich annotations, 100% schema coverage and no output schema, the description covers the essentials including the response structure. It could say more about volume/pagination given the '100+ item list', but the categories parameter and schema already handle narrowing.

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, but the description adds concrete fuzzy-match examples ('car camping', 'camping with kids') that go past the schema's generic 'Common phrasings are also accepted'. The categories parameter is not discussed, though the schema documents it well.

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 ('Get a full Wilderness Times packing checklist for one activity') plus the shape of the result (organised by category, with buying-guide links). It implicitly separates itself from list_checklists and build_checklist by being a single-activity retrieval, but never names a sibling explicitly.

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?

'Answers what to pack for a trip' gives the use case, and 'one activity' implies the scope, but there is no when-not guidance and no alternative named (e.g. use build_checklist to customise, get_checklist_pdf for a printable). Usage is inferable rather than stated.

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