Skip to main content
Glama

Search Whoppah listings

search_catalog
Read-onlyIdempotent

Search Whoppah's live catalogue of curated second-hand design: furniture, lighting, art, decor and designer bags, every listing screened by Whoppah's curators. Use it when someone wants to find, compare or buy a second-hand design piece listed on Whoppah. Combine a free-text query with filters (category, brand, designer, price range in EUR, condition, colour, material, seller country) and narrow further with the facet counts in the result. Every result can be bought or bid on right now: sold, reserved and expired listings never appear. Each item carries its whoppah.com link; give the buyer that link, because buying and payment happen on whoppah.com.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNo
brandNo
colorNo
limitNo
queryNo
countryNo
categoryNo
designerNo
languageNoThe buyer's language: titles come back as whoppah.com shows them in it, and links open the listing's page in it.en
materialNo
conditionNo
price_maxNo
price_minNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "default": "en",
      +  "description": "The buyer's language: titles come back as whoppah.com shows them in it, and links open the listing's page in it.",
      +  "enum": [
      +    "en",
      +    "nl",
      +    "de",
      +    "fr",
      +    "es",
      +    "it"
      +  ],
      +  "title": "Language",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds genuinely new behaviour: only live listings appear (sold, reserved and expired are excluded), facet counts in the response can drive further narrowing, each item carries a whoppah.com link, and buying/payment happen off-tool on whoppah.com. The main omission is pagination behaviour — nothing about how page and limit interact, defaults, or result-set size caps.

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 purpose and use case, then filters, then the freshness guarantee, then the buyer handoff — a sensible order with no filler sentences. Minor slack from promotional phrasing about curation ('every listing screened by Whoppah's curators') that repeats the 'curated' claim already made earlier.

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?

An output schema exists, so return values need no explanation, and the description correctly focuses on scope, filter composition, result freshness and the crucial instruction to hand the buyer the whoppah.com link. For a fourteen-parameter search tool the remaining gap is pagination and sorting guidance, which an agent would otherwise have to guess.

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 only 7%, so the description carries most of the burden; it does well for the domain filters by mapping them to meaningful dimensions (category, brand, designer, price range explicitly in EUR, condition, colour, material, seller country) and for query as free text. However, sort, page and limit are never explained in the description or schema, leaving three of fourteen parameters semantically undefined.

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 Whoppah's live catalogue of curated second-hand design, enumerating the domains covered (furniture, lighting, art, decor, designer bags). This is clearly distinguishable from siblings such as get_item or similar_items, which retrieve a single known item or recommendations rather than performing a catalogue search.

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?

Gives explicit when-to-use guidance: 'Use it when someone wants to find, compare or buy a second-hand design piece listed on Whoppah,' plus how to use it (combine free-text query with filters, then narrow via facet counts). It does not name alternatives or when NOT to use it — e.g. pointing to similar_items for lookalikes or get_item once a listing is chosen — so there is no routing exclusions.

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