Skip to main content
Glama

Megamarket Search

megamarket_search
Read-onlyIdempotent

Search Megamarket product listings by query and return prices and availability based on the configured delivery address or logged-in profile address.

Instructions

Search the Megamarket catalog via the mobile API, inside the operator's Chrome.

Prices and availability depend on the delivery address: by default a public city-level one (MEGAMARKET_ADDRESS); only with MEGAMARKET_USE_PROFILE_ADDRESS=1 does the logged-in profile's default address win — that reads a private account endpoint, and the response says so in _meta.warnings ("address_source:profile" plus a "profile_address_read" notice). Any warning that is not prefixed "info:" makes _meta.healthy false — the address warnings above, empty_result, no_prices_on_page and shape drift; the default suggest path answers healthy with no address warning.

price_rub is None when the tile states no price — never 0.

Full field list and error codes: guide://megamarket/megamarket_search.

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": "megamarket_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text, e.g. 'стиральная машина'

Output Schema

NameRequiredDescriptionDefault
_metaNo
countNo
itemsNo
queryNo
statusNo
tier_usedNo
total_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, but the description goes well beyond them: it discloses that prices are address-dependent, that MEGAMARKET_USE_PROFILE_ADDRESS=1 triggers a private account endpoint read, and that this is surfaced in _meta.warnings. It also defines the health rule (any non-"info:" warning makes _meta.healthy false) and the price_rub=None-not-0 convention, which is exactly the non-obvious behavior an agent needs.

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 core purpose is front-loaded in the first clause, and the operational caveats follow in a logical order (address → warnings → health → price sentinel → guide pointer). It is dense and somewhat long for one parameter, but essentially every sentence carries information an agent cannot get from the schema.

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 one-parameter search tool with an output schema, the description covers the remaining unknowns: environment-dependent address behavior, warning/health semantics, and the null-price convention, plus a guide URI for the full field and error list. Nothing required to interpret results correctly is missing.

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?

There is a single required parameter with full schema description coverage, including an example, so the schema already carries the semantics. The description adds no query-syntax guidance (length limits, language, wildcards) beyond what the schema states, making 3 the right baseline.

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?

"Search the Megamarket catalog via the mobile API" states a specific verb and resource and even names the transport, so an agent knows exactly what this does. It does not explicitly contrast with megamarket_card (the likely drill-down alternative), so sibling differentiation is left implicit rather than stated.

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?

Usage is implied by the verb "Search" — use it to find products in the Megamarket catalog. There is no explicit when-to-use/when-not-to-use statement and no named alternative (e.g. megamarket_card for a known product), so the agent must infer routing.

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