Skip to main content
Glama

Megamarket Product Card

megamarket_card
Read-onlyIdempotent

Fetch one Megamarket product card by item ID or product URL to view product details, current price, and old price.

Instructions

Fetch one Megamarket product card.

price_rub and old_price_rub are None when the card states none — never 0.

Full field list and error codes: guide://megamarket/megamarket_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": {
      "item_id_or_url": "<item_id_or_url>"
    },
    "name": "megamarket_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_id_or_urlYesGoods id or megamarket.ru product URL

Output Schema

NameRequiredDescriptionDefault
urlNo
_metaNo
titleNo
ratingNo
statusNo
item_idNo
price_rubNo
tier_usedNo
is_availableNo
rating_countNo
old_price_rubNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds real behavioral value beyond them by specifying the null-vs-0 sentinel convention for price_rub and old_price_rub and by pointing to a guide resource for error codes, though it does not describe failure behavior inline.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short lines, front-loaded with the action, then the highest-risk data caveat, then a reference pointer. No sentence is filler and the ordering reflects what an agent needs first.

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?

An output schema exists, so return-value enumeration is legitimately delegated, and the description covers the one semantic trap (null prices). The guide:// reference covers the full field list and error codes, which is acceptable but means error handling is only reachable via an external resource rather than the definition itself.

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 is fully documented in the schema as a goods id or megamarket.ru product URL. The description adds no further detail such as accepted URL formats or id validation rules, so the baseline of 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?

"Fetch one Megamarket product card" is a specific verb plus a specific resource and scope (single item), which distinguishes it from the search-style siblings by implication. It does not name megamarket_search explicitly, so the differentiation is inferred 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?

The singular-resource framing implies this is the identifier-based lookup to use once you already know an item id or URL, with search being the alternative. However, no when-to-use/when-not-to-use rule or alternative tool is stated, leaving routing to inference from the sibling names.

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