Skip to main content
Glama
sepehr071

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List grocery stores

market_stores
Read-onlyIdempotent

Find SnappMarket stores that deliver to a given latitude and longitude, showing delivery fees, minimum orders, and ratings so you can choose a store before browsing its products.

Instructions

List SnappMarket stores delivering to the point, with delivery fee, minimum order and rating.

Use to pick a store before browsing it with market_store_products.

Input Schema

NameRequiredDescriptionDefault
latYesDelivery point latitude.
longYesDelivery point longitude.
pageNoPage, from 0.
sortNoOrder of the stores.lowest_delivery_price

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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 / 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 / page / description
      Previous value: -"Page number, from 0."New value: +"Page, from 0."
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"market_storesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "market_storesDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds that results are geo-scoped to a delivery point and discloses the surfaced fields, which is useful, but it says nothing about pagination behavior, result caps, or what happens when no store delivers to a point.

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 sentences, zero filler. The capability statement comes first and the routing guidance second, so the agent gets the essential information immediately.

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?

No output schema exists, and the description compensates by naming the key returned fields (delivery fee, minimum order, rating). Combined with the fully documented input schema, an agent has enough to call it correctly; only edge-case and pagination behavior is unaddressed.

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, page and sort are already documented with ranges and enum values. The description only hints at the geo requirement ('delivering to the point') and the rating/fee fields that sort operates on, adding little beyond the schema. Baseline 3 applies.

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 (List) and resource (SnappMarket stores) plus the scope qualifier (delivering to the point) and names what it returns (delivery fee, minimum order, rating). It also names the sibling market_store_products, so an agent can distinguish it without inspecting schemas.

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

Usage Guidelines4/5

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

Explicitly gives the use case: 'Use to pick a store before browsing it with market_store_products,' which establishes a clear ordering relative to that sibling. It stops short of excluding the other plausible alternatives (market_search, market_find_cheapest, market_store_info), so 4 rather than 5.

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