Skip to main content
Glama
Sign In
shopino-mcp

shopino-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Product details

sh_product
Read-onlyIdempotent

Retrieve one product's full details—price, color and size variants with stock, size guide, description, tags, shop trust signals, and shop-site link—to verify availability and seller reliability.

Instructions

Get one product's full record: price, every color / size variant with its own price and stock, size guide, description, tags, the selling shop with trust signals, and the shop-site link.

Use when the user picks a product, to check their size / color is in stock and the shop is trustworthy. Same item elsewhere: sh_similar. More from the shop: sh_browse(shop_id=...). Related: sh_browse(tag=...).

Input Schema

NameRequiredDescriptionDefault
full_textNoReturn size guide and description uncut.
product_idYesProduct id from sh_search / sh_browse, e.g. 2578018.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return size guide and description uncut.",
+  "type": "boolean"
+}
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • removedInput schema / title
      Removed value: -"sh_productArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "sh_productDictOutput",
-  "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 readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral value by spelling out the shape of the returned payload (variants each carrying their own price and stock, trust signals on the selling shop) — information the annotations do not convey. It stops short of noting any rate limiting or truncation behavior beyond what the full_text param implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The what-it-returns inventory is front-loaded and the routing alternatives are compressed into a single dense line with no filler. The first sentence is a long comma-chained list, which is efficient but slightly taxing to parse; otherwise every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the burden of describing return content — and it does, enumerating every significant field of the product record. For a two-parameter, single-record lookup with annotations covering safety, nothing an agent needs to call this correctly is missing.

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 product_id and full_text are already documented in the schema, including the "uncut" semantics of full_text and the example id. The description only alludes to these fields indirectly by listing size guide and description as part of the record. Baseline 3 is appropriate 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?

The description opens with a specific verb+resource ("Get one product's full record") and enumerates exactly what that record contains — price, per-variant price/stock, size guide, description, tags, shop trust signals, site link. That level of detail lets an agent distinguish this from sh_similar, sh_browse, and sh_shop without opening any schema.

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?

It states the triggering condition ("when the user picks a product"), the purpose of the call (check size/color stock and shop trustworthiness), and then names three concrete alternatives with the parameter that selects each: sh_similar for the same item elsewhere, sh_browse(shop_id=...) for more from the shop, sh_browse(tag=...) for related items. This is explicit routing, not 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