Skip to main content
Glama
Sign In
zoomit-mcp

zoomit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get sellers and price history

zm_prices
Read-onlyIdempotent

Compare seller offers by price and view a product's price history to identify lower-cost options or check whether prices have dropped.

Instructions

List a product's seller offers (cheapest first, Toman, with listing title and link) and its price history.

Use for "where is it cheapest" or "has the price dropped". Phones are often listed unregistered; use registered_only for the legal price.

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": {
      "slug": "<slug>"
    },
    "name": "zm_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOnly this city (Persian), e.g. تهران.
slugYesProduct slug from zm_search/zm_list, e.g. apple-iphone-17-pro (or its zoomit.ir URL).
limitNoMax seller offers.
historyNoPrice-history window.3months
registered_onlyNoDrop listings marked unregistered (بدون رجیستری); unmarked stay.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety burden is light; the description adds output shape (title + link, price-sorted), currency semantics, and a data-quality caveat about unregistered listings. It doesn't mention offer-count limits or how the history window interacts with the offer list, so it's not fully transparent.

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, purpose and output shape front-loaded, then usage triggers, then a caveat — no repetition of schema fields. The closing clause ('use registered_only for the legal price') is slightly compressed and takes a moment to parse, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the full burden of describing returns — and it does: ranked seller offers with title and link, currency, plus a price-history series. Combined with a 5-parameter, fully documented schema and complete annotations, nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, but the description adds real meaning beyond the schema: it explains the ordering and currency of offers and, critically, why `registered_only` matters (unregistered phone listings vs. the legal price) — a rationale the schema field text only partially conveys.

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 and resource ('List a product's seller offers ... and its price history') and immediately pins down scope details an agent needs: cheapest-first ordering, Toman currency, and returned fields (listing title and link). This makes it distinguishable from inventory-browsing siblings like zm_guides or zm_filters without opening their schemas.

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?

Gives concrete user-intent triggers ('where is it cheapest', 'has the price dropped') plus a domain-specific routing rule: when phones are listed unregistered, use registered=true-ish filtering for the regulated price. It stops short of naming an explicit alternative sibling (e.g. zm_compare for side-by-side comparisons), so it's clear-context rather than explicit when/when-not routing.

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