Skip to main content
Glama
Sign In
DigiSnap-MCP

DigiSnap-MCP

by yusi20006-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_snappshop_product

Fetch a normalized SnappShop product by ID, including variants and offers, so AI clients can compare prices, sellers, and availability.

Instructions

Get one normalized SnappShop product with variants and offers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>"
    },
    "name": "get_snappshop_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses only that the result is 'normalized' and includes variants and offers. It says nothing about what happens on an unknown product_id, authentication or rate-limit requirements, or whether the data is cached or live.

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?

One short sentence with no filler, front-loading the verb and resource. Every word earns its place.

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

Completeness3/5

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

For a single-parameter read tool with no output schema, the description at least tells the agent what comes back (variants and offers), which is genuinely useful. However it omits ID format, failure behavior, and any hint of result structure, leaving an agent with real gaps before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single product_id parameter is described nowhere beyond its title. The description does not state the ID's expected format, source, or whether it is a numeric SnappShop ID, so it fails to compensate for the coverage gap.

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?

States a specific verb (Get) and resource (one normalized SnappShop product) and even enumerates the payload contents (variants and offers), which distinguishes it from list-style siblings like list_stores and search_snappshop. It does not explicitly name get_digikala_product as the analogous-but-different sibling, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus get_digikala_product, search_snappshop, or the compare_* tools. Usage is only inferable from the word 'one' implying a single known product_id.

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