Skip to main content
Glama
IamMichael23

rangeview-mcp

by IamMichael23

Search products

search_products

Search a catalog of over 5,600 products using free-text, category, caliber, brand, price, stock, and sale filters. Caliber and brand expand from everyday spellings to catalog terms.

Instructions

Search the Rangeview Sports catalog (~5,600 products). Combine free-text with category, caliber, brand, price range, stock and sale filters. Caliber and brand accept everyday spellings ('223', '6.5 Creedmoor') and are expanded to every matching catalog term. Returns compact records; call get_product for full detail. Note only ~34% of the catalog is in stock — pass in_stock_only for buyable items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based
sortNoDefault: relevance with a query, popularity without
brandNoBrand name, e.g. 'Tikka', 'Sig Sauer'
limitNoResults per page (1-50, default 10)
queryNoFree-text search, e.g. 'Tikka T3x' or 'red dot'
caliberNoCaliber, e.g. '223', '6.5 Creedmoor', '12 gauge'
categoryNoCategory name, slug, or id. Use list_categories to browse.
max_priceNoMaximum price in CAD dollars
min_priceNoMinimum price in CAD dollars
attributesNoOther attribute filters, e.g. {"Action":"Bolt Action"}. See list_filter_values.
on_sale_onlyNoOnly items on sale
in_stock_onlyNoOnly currently in-stock items
include_test_productsNoInclude internal $0.01 test rows, hidden by default
Behavior5/5

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

With no annotations, the description discloses key behaviors: spelling expansion for caliber and brand, compact record return, stock percentage, and hidden test products. This provides full transparency beyond what the schema offers.

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?

Four sentences, no wasted words, front-loaded purpose, logical flow from main function to details to a practical note about stock. Ideal conciseness.

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?

Given 13 parameters, no output schema, and nested objects, the description covers scope, filtering capability, special behaviors, stock context, and directs to sibling tools for more detail. Everything an agent needs to know is present.

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%, but description adds value by explaining that caliber and brand accept everyday spellings and are expanded to matching catalog terms, which is not in the schema. Baseline 3, extra context raises to 4.

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?

The description clearly states it searches the Rangeview Sports catalog (~5,600 products), combines free-text with multiple filters, and distinguishes from siblings by mentioning get_product for full detail and list_categories for browsing categories.

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?

Explicitly tells when to use this tool vs alternatives: 'Returns compact records; call get_product for full detail' and suggests using in_stock_only for buyable items due to low stock percentage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IamMichael23/rangeview-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server