Skip to main content
Glama
sepehr071

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Grocery store details

market_store_info
Read-onlyIdempotent

Retrieve a store's delivery fee, minimum order, hours, rating, and coupons before recommending it. Use the data to confirm basket cost plus fees reaches the minimum order.

Instructions

Get one store's delivery fee, minimum order, opening hours, rating and coupons for the point.

Use before recommending a store. Basket cost = sum(final prices) + delivery_fee - coupon, and it must reach min_order. Read each coupon's conditions; is_applicable is false when logged out.

Input Schema

NameRequiredDescriptionDefault
latYesDelivery point latitude.
longYesDelivery point longitude.
vendor_codeYesStore code from market_search / market_stores, e.g. '32xxwe'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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"
    • removedInput schema / properties / vendor_code / title
      Removed value: -"Vendor Code"
    • removedInput schema / title
      Removed value: -"market_store_infoArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "market_store_infoDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description still adds real behavioral context beyond them. Specifically it warns that coupons carry conditions and that is_applicable returns false when logged out, plus that results are point-dependent. That is meaningful disclosure on top of the annotations.

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?

Front-loaded with the payload enumeration, then usage, then caveats — a sensible ordering with no filler. The basket-cost formula sentence is useful for interpreting delivery_fee and min_order, though it is slightly tangential since this tool does not compute baskets itself.

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, the description takes on the burden of describing returns and does so by naming the key fields. Read-only/idempotent semantics are covered by annotations, and the logged-out coupon caveat closes the main behavioral gap. Only minor omissions remain (no mention of failure behavior for an invalid vendor_code).

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%, including the vendor_code pattern and its sourcing from market_search / market_stores, so the schema carries the parameter burden. The description only hints at the geo scope via 'for the point' and adds no format or sourcing detail beyond what is already documented. Baseline 3 is appropriate.

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 and resource (get one store) and enumerates exactly what is returned: delivery fee, minimum order, opening hours, rating and coupons. The scope qualifier 'for the point' plus 'one store's' cleanly separates it from list-oriented siblings like market_stores and market_search. An agent can tell what this tool yields without opening the schema.

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?

'Use before recommending a store' gives a concrete when-to-use context, which is more than most siblings offer. It does not name an alternative or a when-not condition (e.g., vs. market_store_products or market_reviews), so it stops short of full routing guidance.

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