Skip to main content
Glama
shopino-mcp

shopino-mcp

by sepehr071

Find shops

sh_shops
Read-onlyIdempotent

Find shops by name, category, gender, or courier city, and view ratings, surveys, followers, and product counts. Retrieve shop IDs for follow-up browsing or product searches.

Instructions

Find shops by name, category group, gender or courier city, with rating, surveys, followers and product count.

Use to get a shop_id for sh_shop / sh_browse / sh_search.

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": "sh_shops"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoSame-day courier city, e.g. 'تهران'.
pageNoPage number, from 1.
limitNoShops per page.
orderNomost_followed = Instagram followers; newest = newest on Shopino.relevance
queryNoShop name, e.g. 'پاپیون' or 'papion'.
genderNoOnly women's or men's shops.
category_groupNoOnly shops selling this group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv0.5.0
    • removedInput schema / properties / category_group / anyOf
      Removed value: -[
      -  {
      -    "enum": [
      -      "clothing",
      -      "shoes-and-bags",
      -      "accessory"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / category_group / enum
      Added value: +[
      +  "clothing",
      +  "shoes-and-bags",
      +  "accessory"
      +]
    • addedInput schema / properties / category_group / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / city / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 40,
      -    "minLength": 2,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / city / maxLength
      Added value: +40
    • addedInput schema / properties / city / minLength
      Added value: +2
    • addedInput schema / properties / city / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / gender / anyOf
      Removed value: -[
      -  {
      -    "enum": [
      -      "women",
      -      "men"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / gender / enum
      Added value: +[
      +  "women",
      +  "men"
      +]
    • addedInput schema / properties / gender / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 60,
      -    "minLength": 2,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / query / maxLength
      Added value: +60
    • addedInput schema / properties / query / minLength
      Added value: +2
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed11 schema fields changedv0.3.0
    • removedInput schema / properties / category_group / title
      Removed value: -"Category Group"
    • changedInput schema / properties / city / description
      Previous value: -"Only shops with same-day courier delivery here, e.g. 'تهران'."New value: +"Same-day courier city, e.g. 'تهران'."
    • removedInput schema / properties / city / title
      Removed value: -"City"
    • removedInput schema / properties / gender / title
      Removed value: -"Gender"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • changedInput schema / properties / order / description
      Previous value: -"relevance (Shopino's order), most_followed (Instagram followers) or newest on Shopino."New value: +"most_followed = Instagram followers; newest = newest on Shopino."
    • removedInput schema / properties / order / title
      Removed value: -"Order"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"sh_shopsArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "sh_shopsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is fully covered. The description adds the useful detail of which attributes come back per shop, but says nothing about result ordering defaults, pagination caps, or empty-result behavior beyond what the schema shows.

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 padding: the capability and filter/return scope come first, and the routing hint to sibling tools comes second. Nothing is repeated from the schema or annotations.

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 usefully names the per-shop fields returned, which is information the agent could not get elsewhere. Combined with the shop_id routing hint, it covers what an agent needs to call a 7-parameter, all-optional filter tool correctly; only sorting and pagination conventions are left implicit.

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%, with enums documented for order, gender and category_group, so the schema does the heavy lifting. The description only restates the filter dimensions at a high level and adds no syntax, matching, or combination guidance (e.g. whether query is fuzzy or transliteration-tolerant) beyond the schema.

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 gives a specific verb and resource ('Find shops') and enumerates the filterable dimensions (name, category group, gender, courier city) plus the fields returned (rating, surveys, followers, product count). It also distinguishes itself from sh_shop by framing itself as the lookup that produces a shop_id.

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 states the follow-on purpose: 'Use to get a shop_id for sh_shop / sh_browse / sh_search', which tells the agent when this is the right entry point versus going straight to a detail or product tool. It stops short of stating when NOT to use it (e.g. product-level search via sh_search), which keeps it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.