Skip to main content
Glama
Sign In
zoomit-mcp

zoomit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List buying guides

zm_guides
Read-onlyIdempotent

Lists Zoomit buying guides for a category and returns article links for recommendations, including phones under a budget. Use it to find what Zoomit recommends before listing matching products.

Instructions

List Zoomit's buying guides ("best phones under...", "best gaming phones") of a category with their article links.

Use for "what does Zoomit recommend". Next: zm_list with buying_guide=.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based.
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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds that results carry article links, but says nothing about pagination behaviour or result size even though a page parameter exists. With annotations doing the heavy lifting, this is adequate rather than rich.

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, zero filler, with the core purpose front-loaded and the chaining hint placed last. Every clause carries information the agent needs.

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 simple two-parameter read tool with complete annotations, the description covers what is returned (guides plus article links) and what to do next. The only gap is pagination semantics, which the schema's page default and minimum partly mitigate.

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%, so both the category slug (with a pointer to zm_categories) and the 1-based page number are already documented in the schema. The description only implies category scoping and adds no format or usage meaning beyond that, so the baseline 3 applies.

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?

The description names a specific verb and resource ("List Zoomit's buying guides") and scopes it to a category, backed by concrete example titles ("best phones under...", "best gaming phones"). It also points at the sibling zm_list as the follow-up, so an agent can place it in the toolset without opening the schema.

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 an explicit trigger phrase ("what does Zoomit recommend") and a concrete next step ("Next: zm_list with buying_guide=<title>"), which is stronger than most list tools. It does not state when not to use it or how it differs from content-oriented siblings like zm_articles or zm_reviews, leaving that inference to the agent.

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