Skip to main content
Glama

Lamoda Product Card

lamoda_card
Read-onlyIdempotent

Fetch Lamoda product card details by SKU or URL, using GraphQL over HTTPS with an in-page Chrome POST fallback when needed.

Instructions

Fetch a GraphQL card over HTTPS, falling back to an in-page Chrome POST.

Full field list and error codes: guide://lamoda/lamoda_card.

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": {
      "sku_or_url": "<sku_or_url>"
    },
    "name": "lamoda_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
sku_or_urlYesSKU (MP002XM1RMM3) or lamoda.ru product URL

Output Schema

NameRequiredDescriptionDefault
skuNo
urlNo
_metaNo
brandNo
sizesNo
titleNo
statusNo
price_rubNo
tier_usedNo
is_availableNo
old_price_rubNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: it discloses a two-stage retrieval strategy with an HTTPS GraphQL call falling back to an in-page Chrome POST, which signals possible browser automation, latency and failure modes, and it points to error codes. It stops short of saying what happens when both paths fail.

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 the mechanism front-loaded and the reference doc second; nothing is padded. The transport detail ("GraphQL over HTTPS") is arguably implementation noise for an agent choosing a tool, but it is compact.

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?

An output schema exists and the guide resource is cited for fields and error codes, so return values need not be explained. However, for a tool whose output is the whole point, leaving the card's contents entirely to an external guide means an agent that skips the guide knows little about what it will get back.

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?

Schema coverage is 100% and the single parameter already documents both accepted forms (SKU example and lamoda.ru URL). The description adds no format, normalization or validation detail beyond the schema, so the baseline 3 applies.

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?

"Fetch a ... card" gives a verb and a resource, but the resource is described only by its transport ("a GraphQL card over HTTPS") rather than by what it returns — product details, price, availability. Against siblings like aliexpress_card or ozon_card, the name/title carry most of the differentiation; the description itself does not say what a "card" contains.

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 statement of when to use this tool versus the search siblings (lamoda_search) or when not to use it. The only routing help is a pointer to a guide resource for fields and error codes, which is documentation, not usage guidance.

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