Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_search_filters

Read-onlyIdempotent

Retrieve current filters and sort options for a category query on Ozon, revealing price, brand, delivery time, and category parameters while excluding financial promotions.

Instructions

Показать актуальные фильтры текущей категории и варианты сортировки. Раскрывает цену, бренд, срок доставки и категорийные параметры; исключает финансовые промо.

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": {
      "query": "<query>"
    },
    "name": "ozon_search_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
expandNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/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 still contributes two real behavioral facts beyond them: the result is scoped to the *current* category (state-dependent) and financial promo facets are deliberately filtered out. It says nothing about what happens when no category is active or what the result looks like.

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 compact sentences that front-load the action and then the facet breakdown; the semicolon clause efficiently pairs inclusions with the promo exclusion. No filler, though the dense second sentence would read better as an explicit list of what is and is not returned.

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?

With only two parameters and no output schema this need not be long, but an agent still has to guess how 'query' relates to the claimed 'current category' scope. A single clause stating what the query means and whether a category must be active would make the definition complete.

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

Parameters2/5

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

Schema description coverage is 0% and neither of the two parameters is mentioned. The required 'query' parameter is especially ambiguous — it is unclear whether it carries a free-text query, a category, or a filter context, and the phrase 'текущей категории' actively conflicts with the presence of a required query input. The 'expand' flag is wholly unexplained.

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?

The description names a specific verb and resource: 'Показать актуальные фильтры ... и варианты сортировки' (show the current category's filters and sorting options). It also enumerates which facets are surfaced (price, brand, delivery time, category parameters) and which are excluded (financial promos). It does not distinguish itself from siblings such as ozon_search, so it stops short of a 5.

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?

Usage is only implied: the reference to 'текущей категории' signals the tool is meant to be called inside an existing category context, which hints at when it applies. There is no explicit when-to-use statement, no prerequisites (e.g., that a category must first be selected), and no named alternative.

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