Skip to main content
Glama

Browse products

search
Read-onlyIdempotent

Browse products by text, category or filters, with each product's best price. action: search (filters, sort), trending, most_searched (a country's top queries), rows (home-page rows).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance, price, price_desc, total, discount, popular, rating, newest
brandNoBrand name or array of names, e.g. ["Apple","Samsung"]
limitNoMax rows
queryNoText, model or EAN
actionYesOperation to run; help {topic:"search"} lists each one's arguments
detailNocompact (default) or full
localeNoLanguage, e.g. cs
offsetNoRows to skip
countryNoCountry code, e.g. CZ
on_saleNoOnly discounted
categoryNoCategory slug
in_stockNoOnly in stock
price_maxNoMax product price
price_minNoMin product price

Output Schema

NameRequiredDescriptionDefault
moreNoHow to fetch the next page
limitNo
totalNoAll matches, not just this page
offsetNo
returnedNo
cross_border_noteNo
commission_disclosureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"search\"} lists each one's arguments"
    • addedInput schema / properties / brand / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / brand / description
      Previous value: -"Brand or list of brands"New value: +"Brand name or array of names, e.g. [\"Apple\",\"Samsung\"]"
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default) or full",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "commission_disclosure": {
      +      "type": "string"
      +    },
      +    "cross_border_note": {
      +      "type": "string"
      +    },
      +    "limit": {
      +      "type": "number"
      +    },
      +    "more": {
      +      "description": "How to fetch the next page",
      +      "type": "string"
      +    },
      +    "offset": {
      +      "type": "number"
      +    },
      +    "returned": {
      +      "type": "number"
      +    },
      +    "total": {
      +      "description": "All matches, not just this page",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the output promise of "each product's best price" and the existence of a help mechanism for per-action arguments, but says nothing about pagination behavior, result caps, or locale/country effects despite 14 parameters.

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?

Two sentences, front-loaded with the core capability and then the action taxonomy. The action enumeration is a bit list-like and slightly compressed ("action: search (filters, sort), trending..."), but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema and annotations exist, so return values and safety need not be restated. However, for a 14-parameter multi-action tool the description does not clarify which parameters are valid for which action, deferring that entirely to a separate help call; that is a meaningful gap in an otherwise adequate definition.

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?

With 100% schema coverage the baseline is 3, but the description earns more by tying parameters to actions: filters/sort belong to search, country to most_searched, and rows to home-page content. That mapping is genuinely useful for a 14-parameter tool where the required action determines which arguments matter.

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?

States a specific verb and resource ("Browse products") plus the key output attribute ("each product's best price"), then enumerates the four action modes. This is clear enough to distinguish browsing from sibling tools like product or comparisons, but it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Parentshetical notes on the actions (",search (filters, sort)", "most_searched (a country's top queries)", "rows (home-page rows)") imply when each mode applies, and the schema's action description points to help {topic:"search"} for per-action arguments. There is no explicit when-to-use guidance relative to sibling tools and no statement of 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