Skip to main content
Glama

ALLR Motorcycle Gear Prices

Search motorcycle gear

search_gear
Read-onlyIdempotent

Search ALLR's motorcycle-gear catalog (helmets, jackets, suits, pants, boots, gloves, protection, riding shirts, base layers, communication, luggage, accessories) by free text, and get each product's lowest landed cost for a buyer country, how many retailers carry it, and its allr.io product-page URL. The returned id is the product id accepted by get_product_offers, which has the per-retailer price table. The lowest_landed_price is the cheapest total including shipping, import duty and customs brokerage for country (destination sales tax / VAT is not included) — not a sticker price — and is one number out of a full table; get_product_offers has the per-retailer breakdown.

Input Schema

NameRequiredDescriptionDefault
brandNoRestrict to a brand. Accepts a `slug` or `name` from list_categories_and_brands. Applied as a brand-token filter on the matched products.
limitNoMaximum products to return (1-25).
queryYesFree-text search, e.g. 'agv k6', 'waterproof adventure jacket', 'alpinestars smx-6 boots'. Brand names, model names and model numbers all work.
cursorNoOpaque pagination cursor from a previous call's `next_cursor`. Absent on the first page.
genderNoRestrict to products cut for this rider group, using ALLR's own gender classifier.
countryNoBuyer country (ISO-2, plus 'EU' and 'UK' as market codes). Determines the currency and the landed cost: item price + shipping + import duty + customs brokerage fee. Destination sales tax / VAT is not included. ALLR computes landed cost for these four markets only.US
categoryNoRestrict to a catalog category. Accepts a `slug` from list_categories_and_brands (e.g. 'helmets', 'jackets', 'boots').
max_priceNoHighest acceptable landed price in the country's currency.
min_priceNoLowest acceptable landed price in the country's currency.
certificationNoRestrict to products carrying this safety certification label, e.g. 'ECE 22.06', 'DOT', 'SNELL', 'CE AA'. Matched case-insensitively against the same certification labels the ALLR catalog filters on. A product whose certification ALLR cannot derive from its catalog row returns no `certifications` and is excluded by this filter — the product page is the fuller source for certification.

Output Schema

NameRequiredDescriptionDefault
as_ofYesISO-8601 timestamp at which these prices were assembled.
queryYes
countryYes
resultsYes
currencyYes
next_cursorNoValue accepted as `cursor` for the next page; null when there are no more.
results_cappedYesTrue when the search engine returned its maximum of 50 ranked products, i.e. `ranked_match_count` is a floor on how many products match, not the total.
ranked_match_countYesNumber of RANKED RESULTS this query produced after the requested filters — the pool this call paginates over. ALLR's search engine ranks and returns at most 50 products per query, so this is NOT a catalog-wide match count: when `results_capped` is true, more products match than are rankable in one query. A narrower query (`brand`, `category` or more specific text) produces a ranked pool below the cap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / brand / description
      Previous value: -"Restrict to a brand. Use a `slug` or `name` from list_categories_and_brands. Applied as a brand-token filter on the matched products."New value: +"Restrict to a brand. Accepts a `slug` or `name` from list_categories_and_brands. Applied as a brand-token filter on the matched products."
    • changedInput schema / properties / category / description
      Previous value: -"Restrict to a catalog category. Use a `slug` from list_categories_and_brands (e.g. 'helmets', 'jackets', 'boots')."New value: +"Restrict to a catalog category. Accepts a `slug` from list_categories_and_brands (e.g. 'helmets', 'jackets', 'boots')."
    • changedInput schema / properties / certification / description
      Previous value: -"Restrict to products carrying this safety certification label, e.g. 'ECE 22.06', 'DOT', 'SNELL', 'CE AA'. Matched case-insensitively against the same certification labels the ALLR catalog filters on. A product whose certification ALLR cannot derive from its catalog row returns no `certifications` and is excluded by this filter — check the product page before telling a rider something is uncertified."New value: +"Restrict to products carrying this safety certification label, e.g. 'ECE 22.06', 'DOT', 'SNELL', 'CE AA'. Matched case-insensitively against the same certification labels the ALLR catalog filters on. A product whose certification ALLR cannot derive from its catalog row returns no `certifications` and is excluded by this filter — the product page is the fuller source for certification."
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor from a previous call's `next_cursor`. Omit for the first page."New value: +"Opaque pagination cursor from a previous call's `next_cursor`. Absent on the first page."
    • changedOutput schema / properties / as_of / description
      Previous value: -"ISO-8601 timestamp at which these prices were assembled. Quote it when stating a price."New value: +"ISO-8601 timestamp at which these prices were assembled."
    • changedOutput schema / properties / next_cursor / description
      Previous value: -"Pass as `cursor` for the next page; null when there are no more."New value: +"Value accepted as `cursor` for the next page; null when there are no more."
    • changedOutput schema / properties / ranked_match_count / description
      Previous value: -"Number of RANKED RESULTS this query produced after the requested filters — the pool this call paginates over. ALLR's search engine ranks and returns at most 50 products per query, so this is NOT a catalog-wide match count: when `results_capped` is true, more products match than are rankable in one query. Narrow with `brand`, `category` or a more specific query rather than paging for a total."New value: +"Number of RANKED RESULTS this query produced after the requested filters — the pool this call paginates over. ALLR's search engine ranks and returns at most 50 products per query, so this is NOT a catalog-wide match count: when `results_capped` is true, more products match than are rankable in one query. A narrower query (`brand`, `category` or more specific text) produces a ranked pool below the cap."
    • changedOutput schema / properties / results / items / properties / id / description
      Previous value: -"ALLR product id — pass to get_product_offers."New value: +"ALLR product id, as accepted by get_product_offers."
    • changedOutput schema / properties / results / items / properties / url / description
      Previous value: -"Canonical allr.io product page. Cite this."New value: +"Canonical allr.io product page."
  2. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Buyer country (ISO-2, plus 'EU' and 'UK' as market codes). Determines the currency and the landed cost: item price + shipping + import duty + VAT. ALLR computes landed cost for these four markets only. ASK the rider rather than guessing."New value: +"Buyer country (ISO-2, plus 'EU' and 'UK' as market codes). Determines the currency and the landed cost: item price + shipping + import duty + customs brokerage fee. Destination sales tax / VAT is not included. ALLR computes landed cost for these four markets only."
    • changedOutput schema / properties / results / items / properties / lowest_landed_price / description
      Previous value: -"Cheapest landed total (item + shipping + duty + VAT) in `currency`, or null when no retailer currently prices it."New value: +"Cheapest landed total (item + shipping + duty + brokerage; no sales tax/VAT) in `currency`, or null when no retailer currently prices it."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that `lowest_landed_price` is a total including shipping, import duty and customs brokerage but excluding destination VAT, and that landed cost is computed for only four markets. It also flags the non-obvious behavior that products whose certification ALLR cannot derive are silently excluded by the certification filter.

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 with the search scope and immediately followed by what the results contain, which is the right ordering. It loses a little economy by restating twice that get_product_offers holds the per-retailer breakdown.

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 an output schema present, the description need not enumerate return fields, and it still highlights the key ones (`id`, `lowest_landed_price`, retailer count, URL). Given rich annotations and full schema coverage, nothing an agent needs to call this correctly is missing.

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 all ten parameters are already documented in structured form and the baseline is 3. The description reinforces the meaning of `country` and the landed-price fields but adds little parameter-level detail the schema does not already carry.

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 (search ALLR's motorcycle-gear catalog) and enumerates the covered product categories, so the agent knows the scope precisely. It also explicitly separates its role from get_product_offers by saying the returned `id` feeds that tool's per-retailer price table.

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 routing to get_product_offers for per-retailer breakdowns and to list_categories_and_brands (in the schema) for slugs gives clear context for choosing among siblings. It stops short of explicit when-not-to-use guidance, e.g. whether to query get_deals instead when hunting for discounts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources