Skip to main content
Glama
Yandex Lavka Uzbekistan MCP
by d3d0n

search_products

Find grocery products by query at supplied coordinates, with country-specific storefront or session handling for RU, KZ, and UZ.

Instructions

Search at supplied coordinates. RU/KZ use isolated anonymous storefronts; UZ uses the existing session.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
countryNo
latitudeNo
longitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose something genuinely non-obvious: RU/KZ searches hit isolated anonymous storefronts while UZ reuses the existing session. That is valuable context, but it omits what happens when latitude/longitude are null, whether auth is required, and whether results reflect region-specific pricing or availability.

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 short sentences with no filler, and the coordinate scoping is front-loaded ahead of the regional caveat. The brevity borders on under-specification rather than padding, which is the better failure mode here.

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?

No output schema and no annotations mean the description is the only source of truth, and it is too thin for a five-parameter discovery tool. It covers regional storefront semantics but not fallback behavior for optional coordinates or the shape of returned results.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description must compensate. It only loosely maps to latitude/longitude ("supplied coordinates") and country (RU/KZ/UZ), and says nothing about the required query or the limit default, leaving most parameters undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search at supplied coordinates" states a verb and a scoping constraint, but never says what is being searched (products) or that results are product listings. The RU/KZ/UZ storefront note is distinctive, yet the core resource is left implicit and no sibling tool is named for contrast.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus related siblings such as suggest_address, delivery_location, or detect_delivery_location, which plausibly compete for location-driven lookups. The only conditional logic given concerns country-specific storefront behavior, not tool selection.

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