Skip to main content
Glama
sepehr071

masterkala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Filters of a category or brand

mk_filters
Read-only

Retrieve filter options (brands, colors, attributes) with IDs and price range for a category, brand, or tag page to refine product browsing.

Instructions

List the filters of a category, brand or tag page (brands, colors, attributes) with their ids, and its price range.

Use before mk_browse for a brand, color or feature filter: options map filter id -> name; pass the ids as filter_ids. Non-brand groups are cut to 40 options (omitted = the rest): pass group for all. max_price = most expensive item (Toman).

Input Schema

NameRequiredDescriptionDefault
brandNoBrand slug from mk_brands, e.g. 'mcdodo' or 'anker-fa'.
groupNoReturn only this filter group, in full, e.g. 'رنگ' (color) or 'برند' (brand).
tag_idNoTag id from a /tag/<id>/ link in mk_search pages, e.g. 22246.
category_idNoCategory id from mk_categories or mk_search, e.g. 606 (Bluetooth earbuds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • removedInput schema / properties / brand / title
      Removed value: -"Brand"
    • removedInput schema / properties / category_id / title
      Removed value: -"Category Id"
    • removedInput schema / properties / group / title
      Removed value: -"Group"
    • removedInput schema / properties / tag_id / title
      Removed value: -"Tag Id"
    • removedInput schema / title
      Removed value: -"mk_filtersArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mk_filtersDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, but the description adds real behavioral detail beyond it: non-brand groups are truncated to 40 options, `omitted` holds the remainder, and `group` returns the full set. It stops short of return format or any rate/ordering notes, so it is strong but not 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?

Three tight sentences, front-loaded with the core purpose and then the routing/workflow guidance. The back-half is somewhat dialect-specific and elliptical ('`omitted` = the rest', 'max_price = ... (Toman)'), but nothing is wasted.

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 read-only discovery tool with no output schema, the description adequately conveys what comes back (filter ids with names, price range) and the truncation caveat. An agent has enough to call it correctly and interpret the result, though exact response shape is only implied.

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 100%, so each parameter is already documented in the schema; the baseline is 3. The description reinforces usage (max_price = most expensive item in Toman, `group` semantics, filter_ids linking) but does not add syntax or format detail the schema lacks.

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 ('List the filters') and resource ('of a category, brand or tag page') with concrete examples of what filters are returned (brands, colors, attributes) plus the price range. An agent can distinguish this from mk_categories, mk_brands, and mk_browse without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the downstream alternative and the condition: 'Use before mk_browse for a brand, color or feature filter.' It also explains the workflow contract ('options map filter id -> name; pass the ids as filter_ids') and the workaround for truncation ('pass `group` for all'), leaving little to inference.

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

Deploy Server

Other Tools