Skip to main content
Glama

Lamoda Product Card

lamoda_card
Read-onlyIdempotent

Fetch a Lamoda product card by SKU or URL, using GraphQL over HTTPS and falling back to an in-page Chrome POST 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

C2.9/5.0
Behavior3/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 genuine behavioral context by disclosing a two-stage retrieval strategy (GraphQL over HTTPS, then an in-page Chrome POST fallback), which hints at latency and possible browser dependence, but it never says what triggers the fallback, what failure looks like, or where the error codes live beyond a URI reference.

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 tight sentences with no padding, and the pointer to the guide is an efficient way to offload field and error detail. The structure is slightly off-target, though: it front-loads implementation mechanics instead of the outcome the agent cares about.

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, so return values need not be restated, and the guide URI covers field lists and error codes. Still, for a single-SKU lookup tool the description leaves the agent guessing about scope relative to the sibling search tools and about fallback conditions, which is a real gap for correct invocation.

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 exists and schema coverage is 100%, with the property description already explaining the SKU-versus-URL forms and an example. The description adds no further meaning such as accepted URL variants or behavior for malformed identifiers, 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 GraphQL card" gives a verb and an object, but "card" is internal shorthand and the sentence emphasizes transport (HTTPS, POST fallback) over what the tool actually returns, namely product-card data for a given Lamoda SKU or URL. It does not distinguish itself from the sibling lamoda_search beyond its name, so an agent must infer the split.

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 when-to-use guidance at all: nothing says to call this for a single known product versus lamoda_search for discovery, and no prerequisites (valid SKU, reachable lamoda.ru URL) are stated. The only routing hint is the guide URI, which pushes the decision to an external resource.

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