outdoorithm

by io.github.outdoorithm

Overview Discussions Admin

Search Gear

search_gear

Read-only

Search the Outdoorithm gear catalog by keyword, category, price range, kit, necessity, or recommendation tier.

Returns matching products with prices, verdicts, and purchase links.

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

Input Schema

Name	Required	Description
`limit`	No	Max results (1-20, default 10)
`query`	No	Text search across product name, manufacturer, keywords, and description
`kit_name`	No	Filter by kit (e.g., Basics, Camp Kitchen, Hiking, Cold Weather)
`max_price`	No	Maximum price in USD
`min_price`	No	Minimum price in USD
`necessity`	No	Filter by level — Essential, Helpful, or Optional
`category_name`	No	Filter by category (e.g., Shelter, Sleeping Gear, Furniture, Electronics)
`recommendation_tier`	No	Filter by tier — Our Pick, Value Pick, or Comfort Pick

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedJul 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / category_name / description

Added value: +"Filter by category (e.g., Shelter, Sleeping Gear, Furniture, Electronics)"

addedInput schema / properties / kit_name / description

Added value: +"Filter by kit (e.g., Basics, Camp Kitchen, Hiking, Cold Weather)"

addedInput schema / properties / limit / description
```
Added value: +"Max results (1-20, default 10)"
```
addedInput schema / properties / max_price / description
```
Added value: +"Maximum price in USD"
```
addedInput schema / properties / min_price / description
```
Added value: +"Minimum price in USD"
```

addedInput schema / properties / necessity / description

Added value: +"Filter by level — Essential, Helpful, or Optional"

addedInput schema / properties / query / description

Added value: +"Text search across product name, manufacturer, keywords, and description"

addedInput schema / properties / recommendation_tier / description

Added value: +"Filter by tier — Our Pick, Value Pick, or Comfort Pick"

First observedApr 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds that matching products include prices, verdicts, and purchase links, which is useful output context, but does not disclose result ordering, pagination behavior beyond the limit param, or how absent filters behave.

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?

Two tight sentences, front-loaded with the action and resource, followed by the return summary. No wasted words.

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 a full output schema, complete parameter documentation, and safety annotations already present, the description covers what an agent needs to select and call the tool. It stops short of the 5 mark only because filter-combination behavior (AND vs OR across facets) is left unspecified.

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 description coverage is 100% with 8 well-documented parameters, so the schema carries the parameter burden. The description's facet list mirrors the schema fields (keyword, category, price, kit, necessity, tier) without adding any syntax, precedence, or combination semantics beyond it.

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 (Search) and resource (Outdoorithm gear catalog) and enumerates the searchable facets. It is clearly distinguishable from siblings like search_campgrounds, compare_gear, and get_gear_for_campground without needing their schemas.

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?

The facet list implies usage but gives no explicit when-to-use guidance, no statement of when to prefer this over compare_gear or get_gear_for_campground, and no note that all filters are optional. Adequate but with clear gaps.

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

All outdoorithm tools Inspect

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

Need Help?