Skip to main content
Glama
Sign In
zoomit-mcp

zoomit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List product categories

zm_categories
Read-onlyIdempotent

Lists Zoomit product categories with slugs and Persian names; search by Persian name or slug to get the category slug required by other tools.

Instructions

List the product categories of Zoomit's product database (slug and Persian name).

Use the slug as category in the other tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zm_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoPart of a Persian name or slug, e.g. لپ تاپ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds the useful fact that each entry consists of a slug plus a Persian name and that the slug feeds other tools. It says nothing about coverage (full list vs. filtered) or whether results are cached/stable, which is a modest gap for a small read-only lookup.

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 short sentences, front-loaded with what is returned, then the practical instruction for using the output. Every sentence earns its place with no filler.

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?

There is no output schema, so the description correctly compensates by naming the returned fields (slug and Persian name). For a one-parameter read-only listing tool this is largely complete; only the filtered-vs-full-list distinction and the relationship to zm_filters are missing.

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 single `query` parameter is documented there with an example, so the baseline is 3. The description provides no additional meaning about the parameter and, read alone, could imply an unfiltered enumeration.

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?

States a specific verb and resource ('List the product categories of Zoomit's product database') and even names the returned fields. It is distinguishable from product-search siblings like zm_search or zm_product, though it never clarifies how it relates to the similarly-taxonomy-oriented zm_filters.

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 second sentence gives clear downstream guidance ('Use the slug as `category` in the other tools'), which implies the tool's role as a lookup step. However, it gives no when-not-to-use guidance and does not distinguish this tool from zm_filters, which an agent could reasonably pick for filter-value discovery.

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