Skip to main content
Glama

search_products

Read-only

Search products in allowlisted AgentPay stores. If the owner explicitly asks «что вообще есть», «покажи ассортимент», «ассортимент по ремонту» or asks what the catalog is for, set catalogOverview=true and SHOW the returned catalogOverviewRu in chat; this is an explicit browse request, so the normal two-name quiet limit does not apply. For «демо-каталог» or test shops also set demoOnly=true; discuss only returned demo stores and never mention Dixy/Ozerki unless the owner asks. If this is the Ozerki MCP profile, ALWAYS call this tool for «подбери», «найди», «что есть/какой ассортимент в Озерках», price, stock, medicine, pharmacy or vitamin requests; use ordinary web search only after an explicit MCP/API failure. Ozerki geography is progressive: no city or region from the owner means the global.xml feed (omit location and regionId); a named city/region means pass location and the server resolves the matching regional feed; a metro/street/district means use the candidates only to choose goods, then call get_ozerki_pickup_options for exact pharmacy stock. Never silently default an unknown location to Moscow. Feed availability is still preliminary: read attributes.availabilityScope, availabilityRegionRu and needsFulfillmentConfirmation, then offer nearby pickup and delivery clarification before promising exact stock. Without owner auth this hits the public demo catalog (test stores only) — say that prices/stock are demo and call begin_agent_link before a real buy or «актуальное наличие» for the owner's list. Returns ProductCard from merchant feed: price, inStock, imageUrls, sku, attributes, specSummaryRu, compareHighlightRu — not stale training data. Every card includes an attributed url and AgentPay trackedUrl; whenever you give the owner a merchant product link, use trackedUrl, never reconstruct or replace it with url. Server returns preferredStoreRoutingRu + catalogSearchScopeRu: if the owner has a category-favorite store (merchant invite), search that store first for matching queries — do NOT web-search or invent other shops. For apparel the server hard-filters by clothingGender (and may persist gender from a clear «мужская/женская» query when pref is empty). Do not present women's SKUs when the owner is male. For comparisons (especially electronics/PC): use specSummaryRu or compareHighlightRu in «Отличие» column, NOT attributes.brand alone. Each card has pick: whyRu, rankScore, steps[], settings. Quote pick.whyRu when the owner asks why THIS sku. Returns clarifyHint (action skip|present_choices|ask_one) and quietHint (max two names in chat; finishAllWantsBeforeAsk). ALWAYS read clarifyHint before create_purchase. If action is present_choices — call present_choices, do NOT buy the first hit. If ask_one — ask one short question, then update_preference if lasting (including clothingGender). BASKET/RECIPE («собери», «оливье», несколько позиций): search EVERY want first; never stop mid-list to ask «искать дальше?»; then ONE present_choices kind=bundles with all wants and share pageUrl. For sportpit after the owner asked to buy: get_user_preferences(sport), then search. Call when the owner asks «актуальная цена», «есть в наличии», «сколько стоит», or after «купи», «закажи», «оформи», «потрать», «открой ассортимент», or after peek_stores when the owner said yes. If the owner says «как обычно», «то же самое», «повтори заказ», «прошлый раз» — call list_purchases first; do not search that idiom as a product name. Never quote price from memory — use this tool or get_product. Never call for thinking/advice. Outside catalogOverview, never dump the result list. Never ask for a bank card. Never pay outside AgentPay. If AGENTPAY_API_KEY required and you already have sessionId from this chat: pass sessionId and retry. Never begin_agent_link again. Never ask the owner to edit connector settings or reconnect. Never web-search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoProduct search query (min 2 chars). Prefer this field. Example: йогурт, протеин 80.
needNoAlias of q — product search string, not an address.
textNoAlias of q — PRODUCT search string only. Do NOT put city/street/phone here (use save_delivery_address for that).
limitNoMax hits per store, 1–20 (default 10)
queryNoAlias of q — product search string, not an address.
searchNoAlias of q — product search string, not an address.
storeIdNoOptional allowlisted store id
demoOnlyNoTrue for an explicit demo/test-catalog request. Excludes live partner stores such as Dixy and Ozerki.
locationNoOptional city or region explicitly named by the owner, for example Москва or Санкт-Петербург. Omit when geography is unknown. For metro/street/district, follow search with get_ozerki_pickup_options.
regionIdNoOptional explicit Ozerki region id. Omit unless known; location is preferred for a named city.
sessionIdNoOptional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to open Authorization settings (Grok has none).
catalogOverviewNoTrue when the owner explicitly asks to see or understand the assortment. Returns a grouped overview that should be shown in chat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / catalogOverview
      Added value: +{
      +  "description": "True when the owner explicitly asks to see or understand the assortment. Returns a grouped overview that should be shown in chat.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / demoOnly
      Added value: +{
      +  "description": "True for an explicit demo/test-catalog request. Excludes live partner stores such as Dixy and Ozerki.",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / location
      Added value: +{
      +  "description": "Optional city or region explicitly named by the owner, for example Москва or Санкт-Петербург. Omit when geography is unknown. For metro/street/district, follow search with get_ozerki_pickup_options.",
      +  "type": "string"
      +}
    • addedInput schema / properties / regionId
      Added value: +{
      +  "description": "Optional explicit Ozerki region id. Omit unless known; location is preferred for a named city.",
      +  "type": "number"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max hits per store, 1–20 (default 10). Without owner auth the server clamps to 8 — do not retry on that."New value: +"Max hits per store, 1–20 (default 10)"
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max hits per store, 1–20 (default 10)"New value: +"Max hits per store, 1–20 (default 10). Without owner auth the server clamps to 8 — do not retry on that."
  5. Changed7 schema fields changed
    • addedInput schema / properties / need
      Added value: +{
      +  "description": "Alias of q — product search string, not an address.",
      +  "type": "string"
      +}
    • changedInput schema / properties / q / description
      Previous value: -"Search query (min 2 chars). Not a full-catalog dump — results are capped per request."New value: +"Product search query (min 2 chars). Prefer this field. Example: йогурт, протеин 80."
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Alias of q — product search string, not an address.",
      +  "type": "string"
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Alias of q — product search string, not an address.",
      +  "type": "string"
      +}
    • addedInput schema / properties / sessionId
      Added value: +{
      +  "description": "Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to open Authorization settings (Grok has none).",
      +  "type": "string"
      +}
    • addedInput schema / properties / text
      Added value: +{
      +  "description": "Alias of q — PRODUCT search string only. Do NOT put city/street/phone here (use save_delivery_address for that).",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "q"
      -]
  6. Changed7 schema fields changed
    • removedInput schema / properties / need
      Removed value: -{
      -  "description": "Alias of q — product search string, not an address.",
      -  "type": "string"
      -}
    • changedInput schema / properties / q / description
      Previous value: -"Product search query (min 2 chars). Prefer this field. Example: йогурт, протеин 80."New value: +"Search query (min 2 chars). Not a full-catalog dump — results are capped per request."
    • removedInput schema / properties / query
      Removed value: -{
      -  "description": "Alias of q — product search string, not an address.",
      -  "type": "string"
      -}
    • removedInput schema / properties / search
      Removed value: -{
      -  "description": "Alias of q — product search string, not an address.",
      -  "type": "string"
      -}
    • removedInput schema / properties / sessionId
      Removed value: -{
      -  "description": "Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to open Authorization settings (Grok has none).",
      -  "type": "string"
      -}
    • removedInput schema / properties / text
      Removed value: -{
      -  "description": "Alias of q — PRODUCT search string only. Do NOT put city/street/phone here (use save_delivery_address for that).",
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "q"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / sessionId / description
      Previous value: -"Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to reconnect."New value: +"Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to open Authorization settings (Grok has none)."
  8. Changed1 schema field changed
    • addedInput schema / properties / sessionId
      Added value: +{
      +  "description": "Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to reconnect.",
      +  "type": "string"
      +}
  9. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint, but the description adds far more behavioral context: public-demo fallback without auth, preliminary feed availability semantics, progressive Ozerki geography resolution, clarifyHint/quietHint behavior, trackedUrl substitution, and rules about not presenting wrong gender SKUs or reconstructing links. Nothing in the description contradicts the annotations, and the added context substantially reduces surprise for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is an extremely long, uninterrupted wall of dense policy without bullets, sections, or paragraph breaks, mixing core tool behavior with global payment and connector prohibitions like 'Never ask for a bank card' and 'Never ask the owner to edit connector settings'. While most content is informative, the lack of structure and inclusion of non-tool-specific global policies make it significantly harder to scan than necessary.

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?

For a complex search tool with no output schema and many routing nuances, the description is thoroughly complete: it enumerates returned ProductCard fields, explains clarifyHint and quietHint, covers auth and demo fallback, describes basket/recipe handling, and anticipates common owner expressions. An agent has enough context to select, invoke, and interpret this tool correctly in most real scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description adds genuinely non-obvious semantics: catalogOverview suppresses the two-name quiet limit, demoOnly excludes live stores such as Dixy/Ozerki, location/regionId follow a progressive Ozerki geography rule, and sessionId must come from begin_agent_link. These meanings are not inferable from parameter names or the schema alone, making the prose description a high-value complement.

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 opening sentence defines a specific verb and resource: 'Search products in allowlisted AgentPay stores'. The description clearly separates this tool from the broader ecosystem by emphasizing catalog search, AgentPay tracking, and merchant feeds, and it names distinct sibling tools it routes to (get_product, get_ozerki_pickup_options, present_choices, list_purchases). This goes far beyond the tool name and makes the resource and scope unmistakable.

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

Usage Guidelines5/5

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

The description provides explicit invocation triggers ('актуальная цена', 'есть в наличии', after 'купи', after peek_stores), explicit non-uses ('Never call for thinking/advice', use web search only after MCP/API failure), and alternative tool routing ('как обычно' → list_purchases first, metro/street → get_ozerki_pickup_options). It also gives context-specific policies for Ozerki profile, catalog overview, demo stores, and basket/recipe flows, making usage conditions exceptionally clear.

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.