Skip to main content
Glama
Sign In

Ridgerunner

by com.ridgerunner
OverviewDiscussionsAdmin

Search Ridgerunner products

search_products
Read-onlyIdempotent

Search Ridgerunner's outdoor gear catalog for hunting, fishing, camping, hiking, kayaking and outdoor apparel and footwear, by keywords and optionally by category or brand. Returns products with brand, price, availability, a product photo and a link to buy on ridgerunner.com. Always show each product's photo (the markdown image line in the result) when presenting results.

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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoOptional brand name, e.g. 'KastKing'
limitNoMax results (default 10)
queryNoKeywords, e.g. 'inflatable kayak' or 'tungsten drop shot weights'
cursorNoPagination cursor from a previous call's next_cursor
categoryNoOptional category filter
max_priceNoOptional maximum price in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / brand / description
      Previous value: -"Optional exact brand name, e.g. 'KastKing'"New value: +"Optional brand name, e.g. 'KastKing'"
    • addedInput schema / properties / max_price
      Added value: +{
+  "description": "Optional maximum price in USD",
+  "exclusiveMinimum": 0,
+  "maximum": 100000,
+  "type": "number"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral guidance by specifying returned fields (brand, price, availability, photo, buy link) and instructing agents to always show the product photo when presenting results.

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?

The description is concise, front-loaded with the core search purpose, and each sentence earns its place: scope/filters, return content, and a critical presentation instruction. There is no redundancy or filler.

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?

For a read-only search tool with six well-documented parameters and no output schema, the description sufficiently covers search scope, available filters, return fields, and presentation behavior. It does not explicitly discuss pagination, but the cursor parameter is documented in the schema, so this is a minor gap.

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%, so the parameters are already well documented in the input schema. The description only lightly reiterates that category and brand are optional filters and does not add substantial meaning beyond the schema.

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?

The description clearly identifies a specific verb ('Search') and resource ('Ridgerunner's outdoor gear catalog') and lists supported domains and filters. It does not explicitly contrast itself with sibling tools like get_product_details or compare_products, but the search-and-listing purpose is evident.

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 description implies this tool is for catalog searches by keywords and optional category/brand filters, and that output includes photos and buy links. However, it does not explicitly state when to prefer this over get_product_details or compare_products, leaving sibling selection to inference.

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

All Ridgerunner 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