Skip to main content
Glama
sepehr071

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Restaurant menu

food_menu
Read-onlyIdempotent

Fetch one restaurant's menu with each item's price, discount, packaging fee, and availability so delivery costs and checkout totals can be calculated before ordering.

Instructions

Get one restaurant's menu: every item with price, discount, packaging fee and availability.

Use after picking a restaurant. final_price = price - discount; packaging is added per item at checkout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesDelivery point latitude.
longYesDelivery point longitude.
limitNoMax items.
queryNoOnly items whose title contains this.
vendor_codeYesVendor code, e.g. '947evd' (from food_search / food_restaurants).

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: -100New value: +30
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return."New value: +"Max items."
    • 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 / query / description
      Previous value: -"Only items whose title contains this text."New value: +"Only items whose title contains this."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedInput schema / properties / vendor_code / description
      Previous value: -"Snappfood vendor code, e.g. '947evd' (from food_search / food_restaurants)."New value: +"Vendor code, e.g. '947evd' (from food_search / food_restaurants)."
    • removedInput schema / properties / vendor_code / title
      Removed value: -"Vendor Code"
    • removedInput schema / title
      Removed value: -"food_menuArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "food_menuDictOutput",
-  "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, open-world and non-destructive, so the bar is low; the description adds real domain behavior by stating final_price = price - discount and that packaging is charged per item at checkout. That is value beyond the structured fields, though auth/pagination/rate-limit context is absent.

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, no filler; the core purpose is front-loaded and the pricing rule follows as supporting detail. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only menu lookup with no output schema, the description covers what is returned, when to call it, and how prices resolve. Combined with 100% schema coverage and a full safety annotation set, nothing essential is missing.

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 all five parameters (vendor_code, lat, long, limit, query) are already documented in the schema. The description's price/discount/packaging language describes outputs rather than adding parameter meaning, so 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 (get) and resource (one restaurant's menu) and enumerates the returned fields (price, discount, packaging fee, availability). It clearly differs from restaurant-listing siblings, though it never names an alternative explicitly.

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 after picking a restaurant' gives a clear sequencing cue that places it downstream of food_search / food_restaurants, and the schema notes vendor_code comes from those tools. No explicit when-not-to-use guidance is offered, keeping it short of a 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