Skip to main content
Glama
Sign In
zoomit-mcp

zoomit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List products with filters

zm_list
Read-onlyIdempotent

List products in a chosen category and filter by brand, price, score, specs, stock, or sort to find matching items within a set budget.

Instructions

List one category's products with the site's filters: brand, price, score, specs, stock, sort.

Use for "best/cheapest X under N Toman". Get brand slugs and spec values from zm_filters first.

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": {
      "category": "<category>"
    },
    "name": "zm_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based.
sortNopopular
limitNoMax results.
queryNoText to search in the category.
specsNoSpec filters 'name=value' from zm_filters, e.g. ['رم=8 گیگابایت رم']. Same name twice = either value.
brandsNoBrand slugs from zm_filters, e.g. ['apple','samsung'].
categoryYesCategory slug from zm_categories, e.g. mobile, laptop, vga.
max_priceNoHighest price in Toman.
min_priceNoLowest price in Toman.
min_scoreNoMin user score, whole stars.
priced_onlyNoHide unpriced products (always on for sort=cheapest).
buying_guideNoBuying guide name (or part) from zm_filters; keeps its recommended products.
in_stock_onlyNoOnly products in stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds the useful dependency on zm_filters, but says nothing about result volume, pagination behaviour, or cost of broad queries on an open-world catalog — context that would matter for a 13-parameter listing tool.

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 sentences, both front-loaded: the first establishes scope and capability, the second gives the use case and the prerequisite. No filler, no restatement of the title.

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?

The rich schema and full annotation set carry most of the burden, so the short description is defensible, but with 13 parameters and no output schema the agent gets no signal about what a result looks like or how paging behaves. Adding one line on the return shape or pagination would make it complete.

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 92%, so nearly every parameter is already self-documenting, and the baseline of 3 applies. The description's filter list mostly restates schema field names, and its 'get slugs/values from zm_filters' hint is already repeated in the 'brands' and 'specs' schema descriptions, so it adds little beyond the structured data.

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 gives a specific verb and resource ('List one category's products') and enumerates the filter dimensions it supports (brand, price, score, specs, stock, sort), which maps cleanly onto the schema. It does not, however, distinguish itself from zm_search, the closest sibling, even though this tool also exposes a 'query' parameter — an ambiguity an agent must resolve on its own.

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?

It gives a concrete trigger phrase ('best/cheapest X under N Toman') that tells the agent exactly which user requests this tool serves, and it states a prerequisite workflow step ('Get brand slugs and spec values from zm_filters first'), routing the agent to a sibling before invocation. It stops short of stating when *not* to use it — e.g. when to prefer zm_search for free-text lookups.

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