rozetka-mcp

rozetka_get_product

Resolve a Rozetka product by numeric ID or URL and fetch its description and characteristics for catalog data retrieval.

Instructions

Resolve one Rozetka product by numeric id or product URL. Description and characteristics are fetched by default from product-api; blocked optional catalog hydration does not fail the lookup.

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": {
      "id_or_url": "<id_or_url>"
    },
    "name": "rozetka_get_product"
  }
}

Input Schema

Name	Required	Description	Default
`id_or_url`	Yes
`include_description`	No
`include_characteristics`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that description and characteristics are fetched by default and that a blocked optional catalog hydration does not fail the lookup — a non-obvious degradation guarantee. However, it omits auth/permission requirements, rate limits, and any hint of return shape, which are material for a tool with no output schema.

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?

Two tightly packed sentences with no filler; the core resolution action and input modes lead, and the fallback behavior trails as supporting detail. Every clause carries information.

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?

For a 3-parameter, no-annotation, no-output-schema tool, the definition covers the primary action, the default hydration, and resilience to partial failure. It still leaves the two optional flags' full semantics and the response contents unaddressed, so an agent would have to probe to call it confidently.

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 description coverage is 0%, so the description must compensate. It explains id_or_url (id or URL) and that description/characteristics come back 'by default', which maps to the two boolean toggles, but it never states what suppressing them does or the accepted URL format. Partial compensation for a real coverage gap.

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 ('Resolve') and singular resource ('one Rozetka product') and names both accepted input forms (numeric id or product URL). This cleanly separates it from the plural sibling rozetka_get_products and from rozetka_resolve_url, without needing to open the schema.

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 description implies retrieval context through the id-or-URL input and the default hydration behavior, but it never states when to choose this tool over rozetka_get_products or rozetka_resolve_url, nor any prerequisites or when-not-to-use conditions. Usage is inferable but not guided.

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

Deploy Server