Skip to main content
Glama

SoundCreation Catalog

Search products

search_products
Read-only

Search the SoundCreation catalog by free text (brand, model, category, or keywords), by filters, or both. With a query you get relevance-ranked results; with filters only you get a sorted browse ("cheapest in-stock electric guitar under 2000"). All prices include VAT and are locale-correct. A record with sale_quantity can be bought only in that quantity (for example speakers sold only in pairs): its price is per piece - quote price_for_minimum_quantity and state the rule (sale_quantity.note). sale_quantity.quantity_prices, when present, lists cheaper prices per piece from a quantity (from_quantity, price_per_piece, percent_off).

Input Schema

NameRequiredDescriptionDefault
sortNoDefault: relevance with a query, cheapest-first without one.
brandNoRestrict by brand name, partial match.
limitNoMax results (default 20).
queryNoFree-text search query. Optional if you supply at least one filter.
offsetNoSkip this many results, for paging through a filtered list.
categoryNoRestrict by category name, partial match (use when you do not know the id).
in_stockNotrue = only items physically in stock and shippable now.
languageNoLocale for text + pricing (ro=RON, hu=HUF, de/en=EUR). Default ro.
on_promoNotrue = only items currently discounted (price_old is the pre-discount price).
conditionNonew (default) = normal catalog items. open_box = individually priced used/opened units; each result is one physical unit. bundle = pre-priced sets of several products sold together for less.
max_priceNoHighest acceptable price, in the response currency for the chosen language.
min_priceNoLowest acceptable price, in the response currency for the chosen language.
category_idNoRestrict to one category id. Ids come back on every result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses important business behavior: prices include VAT, pricing is locale-correct, and sale_quantity items can only be bought in that quantity with per-piece pricing rules. It also explains quantity_prices and the need to quote price_for_minimum_quantity.

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 description is front-loaded with purpose and search-mode behavior, then adds pricing and quantity rules. It is dense but nearly every sentence carries useful information, though the final sale_quantity sentence is somewhat compressed.

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 13-parameter search tool with no output schema, the description covers the key behavioral complexities: query versus filter modes, sorting defaults, pricing, locale, and quantity-purchase rules. It does not fully describe the shape of returned records, but the essential calling context 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 description coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by clarifying price semantics (VAT-inclusive, locale-correct) and the special purchasing rules around sale_quantity and quantity_prices.

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 states a specific verb and resource: searching the SoundCreation catalog by free text, filters, or both. It distinguishes the query mode from the filter-only browse mode, but it does not explicitly differentiate itself from siblings such as get_product, list_open_box, or list_promotions.

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?

It clearly explains when to use a free-text query (relevance-ranked results) versus filters only (sorted browse), with a concrete example. It stops short of naming alternatives like list_promotions or list_open_box or stating when not to use this tool.

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