Skip to main content
Glama
Sign In
snapp-mcp

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Discounted restaurants

food_discounted_vendors
Read-onlyIdempotent

Find restaurants with active discounts by location, including any live Gem hunt offer, so users can see which vendors have food deals available now.

Instructions

List restaurants running a discount now, plus the short "Gem" hunt discount if one is live.

Use for "which restaurants have offers". Vendor-level only: food_menu has prices.

Input Schema

NameRequiredDescriptionDefault
latYesDelivery point latitude.
longYesDelivery point longitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / title
      Removed value: -"food_discounted_vendorsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "food_discounted_vendorsDictOutput",
-  "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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral detail beyond that: results conditionally include the short 'Gem' hunt discount when live, and the result set is vendor-level only. That is useful but thin, and no pagination or result-size behavior is described.

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 filler, and the primary purpose plus the sibling-differentiation constraint are front-loaded. The trigger phrase follows immediately after.

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 usefully signals what comes back (vendor-level discount list, optionally including the Gem hunt offer) and the annotations cover safety. It is nearly complete; only result size/ordering behavior is unaddressed for a geo-scoped listing tool.

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% and both parameters (lat, long) carry bounds and meaning in the schema. The description adds nothing about the coordinate parameters, so the 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 and resource ('List restaurants running a discount now') and explicitly delineates its granularity against the sibling food_menu ('Vendor-level only: food_menu has prices'). An agent can distinguish it from food_menu, food_party_deals and food_find_cheapest without opening any 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?

Provides an explicit trigger phrase ('Use for "which restaurants have offers"') and names an alternative for a closely-related need (food_menu for prices). It lacks any when-not-to-use guidance against the other food_* deal tools, so it is clear context without exclusions.

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