Skip to main content
Glama
Sign In
zoomit-mcp

zoomit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search Zoomit articles

zm_articles
Read-onlyIdempotent

Search Zoomit news and review articles by topic or product to find relevant written coverage, including titles, leads, dates, and links.

Instructions

Search Zoomit's news and review articles (title, lead, date, link).

Use for the written review or news about a product.

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": {
      "query": "<query>"
    },
    "name": "zm_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax articles.
queryYesTopic or product name, e.g. بررسی آیفون 17 پرو.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description's useful addition is naming the returned fields (title, lead, date, link), which substitutes for the missing output schema. It says nothing about result ordering, pagination beyond the limit parameter, or the open-world reach implied by openWorldHint=true.

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?

Two short sentences, front-loaded with the resource and returned fields. The second sentence is slightly redundant with the first and the phrase "written review" muddies the line with zm_reviews, but there is 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?

For a two-parameter, read-only search tool with full schema coverage and rich annotations, this is nearly sufficient; listing the returned fields compensates well for the absent output schema. The only real remaining gap is sibling disambiguation against zm_reviews and zm_search, which the complexity of the toolset makes relevant.

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% — query documents itself with a concrete Persian example, and limit states its default and max. The description adds no further meaning such as query matching behavior (exact vs fuzzy, language expectations) beyond the schema. Baseline 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 states a specific verb and resource ("Search Zoomit's news and review articles") and even enumerates the returned fields (title, lead, date, link), which is more than the name alone conveys. It does not, however, differentiate itself from plausible siblings like zm_reviews or zm_search, leaving the agent to guess at the boundary.

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?

"Use for the written review or news about a product" gives an implied when-to-use, which is better than nothing. But with zm_reviews and zm_search in the sibling list, no exclusion or alternative routing is offered, so an agent cannot reliably choose between them from this text alone.

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