Skip to main content
Glama
Sign In
sepehr071

shopino-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Shop profile

sh_shop
Read-onlyIdempotent

Retrieve a shop's profile, including ratings, buyer survey %, followers, product count, categories, courier city, contacts, and website, to judge whether it is trustworthy.

Instructions

Get a shop's profile: ratings, buyer survey %, followers, product count, main categories, courier city, contacts and website.

Use to judge whether a shop is trustworthy. Its products: sh_browse(shop_id=...) or sh_search(shop_id=...); its brands (watch shops): sh_brands.

Input Schema

NameRequiredDescriptionDefault
shopYesShop id or username, e.g. '489' or 'papionlady'.
full_textNoReturn the shop description uncut.
similar_shopsNoAlso list up to 10 similar shops.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return the shop description uncut.",
+  "type": "boolean"
+}
    • changedInput schema / properties / shop / pattern
      Previous value: -"^[A-Za-z0-9._]{1,60}$"New value: +"^[A-Za-z0-9_][A-Za-z0-9._]{0,59}$"
    • removedInput schema / properties / shop / title
      Removed value: -"Shop"
    • removedInput schema / properties / similar_shops / title
      Removed value: -"Similar Shops"
    • removedInput schema / title
      Removed value: -"sh_shopArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "sh_shopDictOutput",
-  "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 and destructiveHint=false, so the safety profile is covered. The description adds useful context about what data is returned, but says nothing about pagination, rate limits, or how 'similar_shops'/'full_text' change the payload.

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?

Three short clauses, front-loaded with the resource and payload, followed by usage and cross-references. Every sentence carries information; 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?

There is no output schema, but the description compensates by enumerating the profile fields returned. It omits any note on response shape or size limits, so it is slightly short of fully complete, but adequate for a read-only profile fetch.

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 'shop', 'full_text' and 'similar_shops' are already documented in the schema. The description adds no syntax, format, or default guidance beyond that, which is the expected baseline when the schema does the heavy lifting.

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 ('Get') and resource ('shop's profile') and enumerates the returned content: ratings, buyer survey %, followers, product count, categories, courier city, contacts, website. It also differentiates itself from siblings by routing product and brand lookups elsewhere.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('judge whether a shop is trustworthy') and names the alternatives with their conditions: products via sh_browse(shop_id=...) or sh_search(shop_id=...), brands via sh_brands. Nothing is left to inference.

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