Skip to main content
Glama
Sign In

checklists

by com.wildernesstimes
OverviewDiscussionsAdmin

Find tents and gear

find_gear
Read-onlyIdempotent

Search Wilderness Times' gear recommendations. TENTS: 350+ tents, each scored out of 10 on its own review page — filter by size (the manufacturer's rating) or how many it realistically sleeps, seasons and weight, and they come back best-scored first. EVERYTHING ELSE (sleeping bags, stoves, coolers, chairs, packs, hatchets and ~60 more categories): returned as the Wilderness Times buying guides that cover it, each with its picks — the guide is the recommendation. Answers what gear to buy, which tent suits a trip, or which of anything taken camping or hiking to choose. Accepts plain words ('tent for a family of 4', 'ultralight backpacking tent', 'camping chair'); filler like 'best' is ignored. With no query it returns what is covered. Tent searches default to car camping unless the question signals backpacking; results are ordered best-scored first. Tent scores are Wilderness Times editorial ratings, not lab tests. Where Wilderness Times has one, an item carries priceRange: a typical price range (e.g. 'usually $300–$400'), an estimate rather than a current price. Current prices are on each linked review page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_gear"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoRestrict to tents or to other gear. Default: any.
sizeNoTents only. The manufacturer's size, the number on the box ('2P', '4 person'); matched exactly.
limitNoHow many tents and how many guides to return. Default 8, maximum 25.
queryNoWhat the user wants, in plain words — a tent type ('ultralight backpacking'), a category ('camping shovel'), a brand or a model. Capacity and seasons in the words are understood too ('4 person' as a size, 'sleeps 4' or 'family of 4' as realistic capacity, '4-season').
sleepsNoTents only. How many people it must REALISTICALLY sleep, by Wilderness Times' count (often below the size); matches that many up to 2 more.
seasonsNoTents only. 3 = at least three-season; 4 = four-season (winter).
maxWeightLbsNoTents only. Heaviest acceptable packed weight in pounds — relevant for backpacking.
includeDiscontinuedNoInclude tents no longer in production. Default false. Relevant to someone who already owns one, is buying used, or asks about an older model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / includeDiscontinued / description
      Previous value: -"Include tents no longer in production. Default false. Set true when the user already owns one, is buying used, or asks about an older model."New value: +"Include tents no longer in production. Default false. Relevant to someone who already owns one, is buying used, or asks about an older model."
    • changedInput schema / properties / maxWeightLbs / description
      Previous value: -"Tents only. Heaviest acceptable packed weight in pounds — use for backpacking."New value: +"Tents only. Heaviest acceptable packed weight in pounds — relevant for backpacking."
  2. Changed3 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"What the user wants, in plain words — a tent type ('ultralight backpacking'), a category ('camping shovel'), a brand or a model. Capacity and seasons in the words are understood too ('4 person', '4-season')."New value: +"What the user wants, in plain words — a tent type ('ultralight backpacking'), a category ('camping shovel'), a brand or a model. Capacity and seasons in the words are understood too ('4 person' as a size, 'sleeps 4' or 'family of 4' as realistic capacity, '4-season')."
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Tents only. The manufacturer's size, the number on the box ('2P', '4 person'); matched exactly.",
+  "type": "number"
+}
    • changedInput schema / properties / sleeps / description
      Previous value: -"Tents only. How many people it must sleep; matches tents sleeping that many up to 2 more."New value: +"Tents only. How many people it must REALISTICALLY sleep, by Wilderness Times' count (often below the size); matches that many up to 2 more."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly/idempotent/non-destructive); the description adds substantive behavior the annotations cannot: default ordering is best-scored first, tent searches default to car camping unless backpacking is signalled, filler words are ignored, scores are editorial not lab tests, and priceRange is an estimate rather than a live price. That last point heads off a very likely misreading of returned data.

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?

Front-loaded well: the TENTS / EVERYTHING ELSE split comes first and is the most decision-relevant content. It is dense but nearly every sentence carries a fact; the priceRange and editorial-rating tail is slightly over-explained for a search tool, keeping it off a 5.

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, and the description compensates fully: it describes both return shapes (scored tents ordered best-first, guides-as-recommendations for other categories), explains the priceRange field, and notes what happens with an empty query. Nothing an agent needs in order to call this correctly or interpret results 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; the description earns an extra point by clarifying the size-vs-sleeps distinction in prose (the box number versus realistic capacity) and by adding query semantics the schema doesn't state — filler like 'best' is ignored, and 'family of 4' or '4-season' in free text are interpreted. It doesn't add anything beyond the schema for limit, seasons, or includeDiscontinued.

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+resource ('Search Wilderness Times' gear recommendations') and then splits the response domain explicitly: TENTS are scored review pages with filters, EVERYTHING ELSE returns buying guides. That split is the key disambiguation an agent needs, and it's spelled out rather than implied.

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?

Gives the exact question shapes it answers ('what gear to buy, which tent suits a trip, which of anything taken camping or hiking'), the accepted input style with worked examples, and the no-query behavior. Siblings (build_checklist, get_gear, etc.) are checklist-oriented and clearly outside this tool's remit, so no explicit exclusion is needed.

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