Skip to main content
Glama

On sale now

on_sale
Read-onlyIdempotent

Find designer clothes, shoes and bags marked down at independent luxury boutiques, with old price, current price, discount, sizes in stock and where to buy.

Instructions

Designer clothes, shoes and bags marked down right now at independent luxury boutiques, each with its old price, the price now, how much is off, the sizes in stock, the shop and the shopwithin.co page to buy it. Use this when someone asks for a designer sale, designer deals or a designer outlet, designer clothes on sale, a price drop, one brand on sale ("Canada Goose sale", "Rick Owens sale"), a kind of item on sale, or Black Friday and Cyber Monday prices. It narrows by designer, kind, women's or men's, size, boutique, city and a price cap, and gives within's sale page or Black Friday page for the designer when there is one. It only knows what the boutiques on within have marked down today.

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

Input Schema

NameRequiredDescriptionDefault
cityNoThe city the boutiques are in, e.g. 'Toronto': a place to shop, not the shopper's own location.
limitNoItems per page, default 12.
orderNobiggest_drop (the default): the biggest markdown first. lowest_price: the cheapest first. newest: among the marked-down items, the ones that arrived at the boutiques last come first.
sizesNoSizes that must be in stock, as the shops label them: 'M', '42', 'US 9', 'IT 38'.
offsetNoItems to skip; use next_offset from the page before.
boutiquesNoBoutique domains to read, as shown on boutiques and items (e.g. 'wdlt117.myshopify.com').
designersNoDesigner or brand names: 'Canada Goose', 'Stussy', 'Rick Owens'.
price_maxNoHighest price now, in the boutique's currency.
categoriesNoKinds of item in plain words: 'jackets', 'hats', 'shorts', 'sneakers', 'bags', 'shoes'.
departmentNoWomen's or men's. Items made for anyone stay in.

Output Schema

NameRequiredDescriptionDefault
noteYes
pagesYes
totalYes
piecesYes
view_urlYes
next_offsetYes
total_is_floorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive, closed-world profile, and the description adds meaningful context beyond them: the result fields, the redirect to within's sale or Black Friday page when one exists, and the important scope caveat that it 'only knows what the boutiques on within have marked down today.' Minor gap: nothing about pagination or empty-result behavior, but the output schema reduces the need.

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?

The purpose is front-loaded in the first sentence, and the final sentence usefully bounds the scope. The middle sentence's long enumeration of near-synonymous query phrasings ('designer sale, designer deals or a designer outlet, designer clothes on sale...') is somewhat repetitive but serves retrieval matching, so the waste is limited.

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 10-parameter, fully documented, zero-required filter tool with an output schema, the description covers purpose, trigger conditions, filterable dimensions, and data-boundary limits. It does not discuss paging through results or what happens when no markdowns match, which are the only remaining gaps.

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 every parameter is already documented, including enums, defaults, and currency notes. The description only restates the filter dimensions (designer, kind, department, size, boutique, city, price cap) without adding format, interaction, or edge-case meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb-and-resource combination ('Designer clothes, shoes and bags marked down right now at independent luxury boutiques') and enumerates the returned fields: old price, current price, discount, sizes in stock, shop, and buy page. It is clearly distinct from siblings such as new_arrivals or search_pieces because it is scoped to marked-down inventory only.

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 description gives explicit when-to-use triggers with concrete query examples ('Canada Goose sale', 'Rick Owens sale', Black Friday/Cyber Monday, price drop, kind of item on sale). It falls short of setting exclusions or naming an alternative sibling to use for full-price or non-sale searches, leaving that routing to inference.

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