Skip to main content
Glama
sepehr071

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Find cheapest groceries

market_find_cheapest
Read-onlyIdempotent

Find in-stock grocery offers near a delivery point and sort them by final price to compare costs; shows delivery fees and minimum orders.

Instructions

Find the cheapest in-stock offers for a grocery product near the point.

Use for the lowest price of an item. Scans open stores that deliver to the point; one flat list sorted by final price. Check delivery_fee and min_order before recommending a store.

Input Schema

NameRequiredDescriptionDefault
latYesDelivery point latitude.
longYesDelivery point longitude.
limitNoMax offers.
pagesNoPages to scan, 12 stores each.
queryYesProduct name, e.g. 'شیر کم چرب'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.2.0
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude of the delivery point (Iran: ~25 to ~40)."New value: +"Delivery point latitude."
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • changedInput schema / properties / limit / default
      Previous value: -20New value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max offers to return."New value: +"Max offers."
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • changedInput schema / properties / long / description
      Previous value: -"Longitude of the delivery point (Iran: ~44 to ~63)."New value: +"Delivery point longitude."
    • removedInput schema / properties / long / title
      Removed value: -"Long"
    • changedInput schema / properties / pages / description
      Previous value: -"Search pages to scan, 12 stores each."New value: +"Pages to scan, 12 stores each."
    • removedInput schema / properties / pages / title
      Removed value: -"Pages"
    • changedInput schema / properties / query / description
      Previous value: -"Product name, Persian works best, e.g. 'شیر کم چرب'."New value: +"Product name, e.g. 'شیر کم چرب'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"market_find_cheapestArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "market_find_cheapestDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description usefully adds behavioral detail beyond them: it scans only open stores that deliver to the point, returns a single flat list sorted by final price, and flags delivery_fee/min_order as requester-side checks. With no output schema, this return-shape disclosure carries real value.

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?

Three short sentences, front-loaded with the core purpose and free of filler. Minor slack in 'near the point' phrasing, but nothing that wastes the agent's attention.

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?

With no output schema and 5 parameters, the description fills the most important gap by describing the return (a flat list sorted by final price) and the post-call checks. It does not explain what limit/pages trade off against latency, but the schema bounds make that largely inferable.

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 lat/long/query/limit/pages are already documented in the schema itself. The description gestures at 'near the point' and 'grocery product' but adds no format, unit, or constraint detail beyond what the schema states; baseline 3 applies.

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 and resource ('Find the cheapest in-stock offers for a grocery product') plus the geographic scope ('near the point'). It distinguishes itself implicitly from the near-identical sibling food_find_cheapest via the 'grocery' framing, but never names that sibling, so the differentiation is left to inference.

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 for the lowest price of an item' states the intended context, and the closing note on checking delivery_fee/min_order is a useful invocation guideline. However, with food_find_cheapest sitting in the sibling list, the absence of any explicit when-not-to-use or alternative-tool routing is a real gap.

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