Skip to main content
Glama

Detsky Mir Product Card

detmir_card
Read-onlyIdempotent

Fetch price, rating, stock, and seller details for one Detsky Mir product by ID, including region-specific physical-store availability and own vs third-party stock.

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, openWorld and non-destructive, so safety is covered. The description adds real value beyond that: region is a per-call override of an environment default rather than a persisted setting, store_count is a count of physical shops that varies sharply by city, and price_rub is None (never 0) when no price is stated — a null-handling rule that prevents misreading 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?

Front-loaded with a one-line summary of what is returned, then progressively deeper detail on region and edge cases. The bold emphasis line and re-verification anecdote are slightly decorative but earn their place by justifying the region guidance; nothing is redundant.

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, idempotent read with an output schema, this covers what an agent needs: scope, region override behavior, null price semantics, and a pointer to guide://detmir/detmir_card for the full field list and error codes. Deferring error codes to a guide is acceptable given a return schema already exists.

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?

Schema description coverage is 100%, so baseline is 3, but the description goes further by explaining the consequence of region (it drives both online price and offline stock counts, with a concrete 152/37/2 city spread) and the override semantics. product_id is the only parameter left to the schema, which documents it 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?

States a specific verb (fetch) and resource (one Detsky Mir product card) plus the exact fields returned: price, rating, stock, seller. It also positions itself against the sibling family by scoping to a single product rather than a category listing (detmir_category).

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 concrete guidance for the region parameter — pass it to ask about a specific city, and it overrides DETMIR_REGION for this call only, enabling city comparisons in one session. It also implies the intended niche (kids-and-baby coverage the general marketplaces handle unevenly), but never explicitly says when to prefer detmir_category or compare_prices over this tool.

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