Skip to main content
Glama
sepehr071

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Grocery product details

market_product
Read-onlyIdempotent

Fetch one product's details and current price from a specific store using product ID and vendor code to verify the cost of an item the user selected.

Instructions

Get one product's details and price in one store.

Use to confirm the current price of an item the user picked.

Input Schema

NameRequiredDescriptionDefault
full_textNoReturn the description uncut (default cut to 400 chars).
product_idYesProduct id from a market_* list.
vendor_codeYesStore code from market_search / market_stores, e.g. '32xxwe'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return the description uncut (default cut to 400 chars).",
+  "type": "boolean"
+}
    • changedInput schema / properties / product_id / description
      Previous value: -"Product id from a market_* product list."New value: +"Product id from a market_* list."
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • removedInput schema / properties / vendor_code / title
      Removed value: -"Vendor Code"
    • removedInput schema / title
      Removed value: -"market_productArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "market_productDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds only the per-store scoping nuance ('in one store'), and says nothing about rate limits, auth, or what the truncated default response looks like.

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 waste, with the core action front-loaded before the usage hint. Nothing redundant or padded.

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 simple read-only lookup with fully documented parameters and no output schema, 'details and price' adequately signals the return content. A brief note on what 'details' includes (or the 400-char truncation default) would make it complete, but the essentials for correct invocation are present.

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 product_id, vendor_code and full_text are fully documented in the schema. The description's 'one product's details and price in one store' loosely reinforces the two required identifiers but adds no format or constraint detail beyond the schema. Baseline 3.

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?

Specific verb and resource: 'Get one product's details and price in one store.' This clearly separates it from list-style siblings like market_store_products or market_search by scoping to a single product. It stops short of naming a sibling explicitly, so it doesn't reach 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 Guidelines3/5

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

'Use to confirm the current price of an item the user picked' gives a concrete usage context, which is better than nothing. However it offers no when-not guidance or routing to alternatives such as market_find_cheapest or market_search when the product id is unknown.

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