Skip to main content
Glama

Detsky Mir Product Card

detmir_card
Read-onlyIdempotent

Fetch price, rating, stock, and seller details for a Detsky Mir product by ID, including region-specific physical store availability.

Instructions

Fetch price, rating, stock and seller for one Detsky Mir product.

Covers the kids-and-baby category that the general marketplaces cover unevenly, and distinguishes Detsky Mir's own stock from third-party marketplace sellers.

Region matters most here. store_count is the number of physical shops holding the item, and it swings hard by city — one item verified live sat in 152 Moscow stores, 37 in St Petersburg, 2 in Khabarovsk. Pass region to ask about a specific city; it overrides DETMIR_REGION for this call only, so one session can compare cities.

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

Full field list and error codes: guide://detmir/detmir_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": {
      "product_id": "<product_id>"
    },
    "name": "detmir_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoISO region code for prices and offline stock, e.g. 'RU-MOW' or 'RU-SPE'. Defaults to DETMIR_REGION.
product_idYesNumeric Detsky Mir product id — the digits in /product/index/id/<id>/.

Output Schema

NameRequiredDescriptionDefault
metaNo
regionNo
productNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so the description's job is lighter — and it adds genuinely new behavior: the per-call region override of DETMIR_REGION (enabling cross-city comparison in one session), the volatility of `store_count` by city with concrete magnitudes, and the rule that price_rub is None rather than 0 when no price is listed. It does not mention auth, rate limits, or freshness/caching, so it is strong rather than exhaustive.

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?

Front-loads the one-line purpose, then uses bold emphasis and a short worked example to make the region caveat unmissable; the guide URI is properly delegated to the end. The Moscow/St Petersburg/Khabarovsk figures are illustrative rather than filler, though the section is slightly longer than strictly needed.

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 two-parameter read-only lookup with an output schema, the description covers the non-obvious parts (null price semantics, region precedence, stock volatility) and offloads field lists and error codes to `guide://detmir/detmir_card`. Nothing essential to a correct call is missing, though the error-code deferral leaves a small external dependency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage the baseline is 3, but the description adds real meaning the schema does not: that `region` controls both prices and offline stock, that it overrides the environment default for this call only, and that shop counts swing dramatically between cities (152 Moscow vs 2 Khabarovsk). `product_id` semantics are left to the schema, which already covers them adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb and resource plus the exact fields returned ("Fetch price, rating, stock and seller for one Detsky Mir product"), then scopes it against the general marketplaces by naming the kids-and-baby category and the own-stock vs third-party distinction. An agent can tell this apart from the generic *_card siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear positive conditions: use it for kids/baby items that general marketplaces cover unevenly, and pass `region` when the question is city-specific, with the note that it overrides DETMIR_REGION for that single call. It stops short of naming an explicit alternative tool or stating when *not* to call it, which keeps it below a 5.

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