Skip to main content
Glama
Sign In

checklists

by com.wildernesstimes
OverviewDiscussionsAdmin

Get gear details

get_gear
Read-onlyIdempotent

Get everything Wilderness Times holds on one tent or product from its gear search: the full review summary, specs, pros and cons, which retailers stock it, and — for a tent — its six category scores, community rating, other sizes of the same model, and two similar tents from other brands. Suited to narrowing to one item, comparing two in detail, or finding what else is like a given tent.

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": {
      "id": "<id>"
    },
    "name": "get_gear"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id shown beside the item in gear search results.
kindNoThe kind from the same result. Optional; it removes ambiguity, since tents and products are numbered separately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The id from a find_gear result."New value: +"The id shown beside the item in gear search results."
    • changedInput schema / properties / kind / description
      Previous value: -"The kind from the same result. Optional, but pass it — it removes any ambiguity."New value: +"The kind from the same result. Optional; it removes ambiguity, since tents and products are numbered separately."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive/closed-world behavior, so safety is covered. The description adds substantial value by disclosing exactly what data is returned (review summary, specs, retailers, category scores, similar tents) — important since no output schema exists.

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?

Two sentences, front-loaded with the core action and payload, no filler. The enumeration of return fields is dense but earns its place since there is no output schema.

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?

With no output schema, the description carries the burden of conveying return contents and does so thoroughly, including the tent-specific extras. An agent has enough to decide and call correctly.

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 both parameters are fully documented in the schema, setting baseline 3. The description only indirectly reinforces the tent-vs-product distinction via the conditional tent-specific fields, without adding syntax beyond the schema.

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 ('Get everything Wilderness Times holds on one tent or product') and enumerates the returned content, distinguishing it from the sibling find_gear search tool by noting the detail depth.

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?

The final sentence gives concrete usage contexts ('narrowing to one item, comparing two in detail, or finding what else is like a given tent'). It implies the gear-search origin but does not explicitly name find_gear as the alternative or state when not to use this tool.

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