Skip to main content
Glama
Sign In
zoomit-mcp

zoomit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Show a category's filters

zm_filters
Read-onlyIdempotent

Lists available filter options—price ranges, brand slugs, spec values, and buying guides—for a product category, so you can check valid filters before querying products by brand or spec.

Instructions

Show what zm_list can filter by in a category: price range, brand slugs, spec filters with values, buying guides.

Call before zm_list when the user asks for a brand or spec.

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_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNoPart of one spec filter's name (e.g. رم) to list all its values; default shows a few per filter.
categoryYesCategory slug from zm_categories, e.g. mobile, laptop, vga.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. Since there is no output schema, the description earns credit for stating what actually comes back (price range, brand slugs, spec filter values, buying guides), which an agent otherwise could not infer. It says nothing about result size or pagination, which keeps it from a 5.

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, zero padding. The scope statement and the returned content come first, then the routing instruction, which is the right order for an agent skimming for a decision.

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 discovery tool with full annotation coverage, the description supplies the missing return-value information and the ordering relationship with zm_list, which is what an agent needs to sequence calls correctly. Only the omission of how to handle large filter sets or the relationship to zm_categories leaves a small gap.

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%, and the schema itself documents both the category slug source and the spec substring behaviour with its default truncation. The description mentions spec filters with values but adds no format or matching semantics beyond that, so the baseline of 3 applies.

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 (show the filters available in a category) and enumerates what is returned: price range, brand slugs, spec filters with values, buying guides. It also ties itself to zm_list, which separates it from the listing sibling. It does not explicitly distinguish itself from zm_categories, which is the other obvious candidate, so it falls 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 Guidelines4/5

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

"Call before zm_list when the user asks for a brand or spec" is an explicit trigger condition plus the alternative it precedes. It does not state when to skip it (e.g. a plain price-only browse), so there is no explicit when-not guidance.

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