Skip to main content
Glama
sepehr071

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List restaurants

food_restaurants
Read-onlyIdempotent

List restaurants delivering to a location, with ratings, delivery fees, ETAs, and coupons. Use to browse or rank restaurants or find a vendor code by name.

Instructions

List restaurants delivering to a point, with rating, delivery fee, ETA and coupon info.

Use to browse or rank restaurants or to find a vendor code by name. No dish prices: use food_menu.

Input Schema

NameRequiredDescriptionDefault
latYesDelivery point latitude.
longYesDelivery point longitude.
pageNoPage of 20, from 0.
sortNoOrder; *_expensive rank by price class, not delivery fee.default
queryNoRestaurant name filter, e.g. 'پیتزا'.
open_onlyNoHide closed or non-delivering restaurants.
has_couponNoWith a coupon only.
has_discountNoDiscounted only.
free_deliveryNoFree delivery only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv0.2.0
    • changedInput schema / properties / free_delivery / description
      Previous value: -"Only restaurants with free delivery."New value: +"Free delivery only."
    • removedInput schema / properties / free_delivery / title
      Removed value: -"Free Delivery"
    • changedInput schema / properties / has_coupon / description
      Previous value: -"Only restaurants offering a coupon."New value: +"With a coupon only."
    • removedInput schema / properties / has_coupon / title
      Removed value: -"Has Coupon"
    • changedInput schema / properties / has_discount / description
      Previous value: -"Only restaurants running a discount."New value: +"Discounted only."
    • removedInput schema / properties / has_discount / title
      Removed value: -"Has Discount"
    • 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 / open_only / description
      Previous value: -"Hide restaurants that are closed or don't deliver here."New value: +"Hide closed or non-delivering restaurants."
    • removedInput schema / properties / open_only / title
      Removed value: -"Open Only"
    • changedInput schema / properties / page / description
      Previous value: -"Zero-based page of 20 restaurants."New value: +"Page of 20, from 0."
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • changedInput schema / properties / query / description
      Previous value: -"Filter by restaurant name, e.g. 'پیتزا' or a brand name."New value: +"Restaurant name filter, e.g. 'پیتزا'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedInput schema / properties / sort / description
      Previous value: -"Order; least_expensive/most_expensive rank by price class, not delivery fee."New value: +"Order; *_expensive rank by price class, not delivery fee."
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"food_restaurantsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "food_restaurantsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so safety is covered. The description adds real value beyond that by disclosing what comes back (rating, fee, ETA, coupon) and, importantly, what does not (no dish prices), which prevents a wrong call.

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 tight sentences with zero waste: the capability and its returned fields come first, then the usage note and the alternative. Nothing is padded or restated.

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 9-parameter listing tool with no output schema, the description covers purpose, key returned fields, and the main boundary against a sibling. Pagination and sort semantics live in the schema, but the absence of any note on result volume or paging behavior is a minor gap.

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 every one of the 9 parameters is documented in-schema, including the sort enum and the price-class caveat, so the description need not repeat them. The description adds no syntax or constraint detail beyond the schema, making the baseline 3 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 ('List restaurants') plus the scope ('delivering to a point') and the payload it returns (rating, delivery fee, ETA, coupon). It also explicitly distinguishes itself from the dish-price sibling by naming food_menu, so an agent can route without opening a 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?

Gives clear usage context ('browse or rank restaurants or find a vendor code by name') and one explicit exclusion pointing at food_menu for dish prices. It stops short of naming other close siblings like food_find_cheapest or food_discounted_vendors, which an agent might also want signposted.

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