Skip to main content
Glama
sepehr071

shopino-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List categories

sh_categories
Read-onlyIdempotent

Retrieve category IDs, URL paths, and levels with product and shop counts to use in search, browse, or cheapest-product tools. Filter by Persian name or English slug for any level.

Instructions

List the category tree with ids, URL paths and levels, plus total product and shop counts.

Use to get a category_id for sh_search / sh_browse / sh_find_cheapest. Without a query only levels up to max_level are listed; with a query every level is searched.

Input Schema

NameRequiredDescriptionDefault
queryNoFilter on Persian name or English slug path, any level, e.g. 'مانتو' or 'sneakers'.
max_levelNoDeepest level without a query (1 = the 14 top categories).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • changedInput schema / properties / max_level / description
      Previous value: -"Deepest level to list when no query is given (1 = the 14 top categories)."New value: +"Deepest level without a query (1 = the 14 top categories)."
    • removedInput schema / properties / max_level / title
      Removed value: -"Max Level"
    • changedInput schema / properties / query / description
      Previous value: -"Optional filter on the Persian name or English slug path, any level, e.g. 'مانتو' or 'sneakers'."New value: +"Filter on Persian name or English slug path, any level, e.g. 'مانتو' or 'sneakers'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"sh_categoriesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "sh_categoriesDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.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 profile is covered. The description adds real behavioral context beyond that: that a query switches the tool from a depth-limited listing to a full-depth search, and that counts are aggregates. Pagination and result-size limits are not mentioned.

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 compact sentences with the output contents front-loaded, followed by the downstream use and the query/max_level behavior. No filler or redundancy.

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?

With no output schema, the description carries responsibility for return values and does describe them (ids, paths, levels, product/shop counts). The parameter interaction is covered too. It stops short of describing ordering, size, or pagination of the returned tree.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the interaction between the two parameters (max_level applies only when query is absent; a query searches every level). That is genuine semantic value above the per-field descriptions.

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 the category tree) and enumerates the returned fields (ids, URL paths, levels, product/shop counts), which distinguishes it cleanly from siblings like sh_brands and sh_shops. An agent knows exactly what this tool produces.

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?

Explicitly routes the agent: use it to obtain a category_id for sh_search / sh_browse / sh_find_cheapest, and explains the two operating modes (no query = levels up to max_level, query = all levels searched). No explicit when-not-to-use case is given, so it falls short of a full 5.

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