Skip to main content
Glama
Sign In
shopino-mcp

shopino-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Similar products

sh_similar
Read-onlyIdempotent

Find similar products at other shops. Use when an item is out of stock or too expensive, or to find the same item cheaper.

Instructions

Find products like this one at other shops (itself left out).

Use when it is out of stock or too expensive, or to find the same item cheaper (kind='visual', sort='cheapest').

Input Schema

NameRequiredDescriptionDefault
kindNovisual = photo-alike products from all shops (to find the same item cheaper); similar = Shopino's 10 related products.visual
sortNorelevance (as returned) or cheapest first.relevance
limitNoMax products to return.
product_idYesProduct id from sh_search / sh_browse, e.g. 2578018.
in_stock_onlyNoOnly products in stock now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.3.0
    • removedInput schema / properties / in_stock_only / title
      Removed value: -"In Stock Only"
    • changedInput schema / properties / kind / description
      Previous value: -"visual = products from all shops whose photo looks like this one (best to find the same item cheaper); similar = Shopino's 10 related products."New value: +"visual = photo-alike products from all shops (to find the same item cheaper); similar = Shopino's 10 related products."
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • changedInput schema / properties / sort / description
      Previous value: -"relevance (as returned) or cheapest first (price to pay)."New value: +"relevance (as returned) or cheapest first."
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"sh_similarArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "sh_similarDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.2/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 structurally. The description adds one genuine behavioral fact beyond that ('itself left out') and the cross-shop search scope, but says nothing about result volume, ordering behavior, or how results are aggregated across shops.

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, no filler, with the core action front-loaded and usage guidance second. The parenthetical exclusion note is placed immediately after the action it qualifies.

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 5-parameter read-only tool with 100% schema coverage and no output schema, the description covers purpose, triggers, and the key parameter pairing. It stops short of describing what the returned product records contain or how the cross-shop results are ordered beyond the sort parameter.

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 description coverage is 100%, so baseline is 3. The description exceeds that by tying parameter values to intent (kind='visual' with sort='cheapest' for the cheaper-alternative use case), which is meaning the schema enumerations alone do not convey.

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 ('find products like this one') plus a scope qualifier ('at other shops') that clearly separates it from sh_search (query-based) and sh_product (single-item detail). The exclusion of the source product is stated explicitly, so an agent knows exactly what the result set contains.

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 trigger conditions ('out of stock or too expensive') and even prescribes a parameter combination for the cheaper-item goal (kind='visual', sort='cheapest'). It does not, however, distinguish itself from the closest sibling sh_find_cheapest, leaving some routing ambiguity.

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