Skip to main content
Glama

Lamoda Search

lamoda_search
Read-onlyIdempotent

Search Lamoda product listings and prices through the operator's Chrome session, enabling marketplace discovery when direct access is blocked.

Instructions

Search Lamoda, rendered in the operator's Chrome (discovery is blocked tier 1).

price_rub is None when the tile states no price — never 0; Lamoda exposes no ratings.

Full field list and error codes: guide://lamoda/lamoda_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": "lamoda_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text, e.g. 'кроссовки nike'

Output Schema

NameRequiredDescriptionDefault
_metaNo
countNo
itemsNo
queryNo
statusNo
tier_usedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds real context beyond that: results come from a browser render in the operator's Chrome, category discovery is unavailable, and price_rub is None (never 0) when absent while ratings do not exist — all of which prevent misreading of results.

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?

Three short, front-loaded lines with no filler; the operational constraint comes first and the data caveats second. The phrase "discovery is blocked tier 1" is terse to the point of being cryptic for an outside reader.

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 single-parameter search tool with an output schema, the description covers the essentials: how results are produced, what is not available, and how to interpret missing price values. It also points to a guide resource for the full field list and error codes, so remaining gaps are deliberately delegated.

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?

Only one parameter, and the schema already documents it at 100% coverage with an example query. The description adds nothing about query syntax, language, or transliteration handling, so the baseline 3 applies.

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+resource ("Search Lamoda") and adds a runtime detail that shapes expectations (rendered in the operator's Chrome). It does not name lamoda_card or explain how this differs from fetching a single product, so sibling differentiation is left implicit.

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 explicit when-to-use or when-not-to-use guidance, and no routing to lamoda_card for product details or to the other marketplace *_search siblings. The parenthetical "discovery is blocked tier 1" hints at a limitation but is unexplained jargon rather than actionable guidance.

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