snapp-mcp

Overview Schema Source Related Servers Discussions Admin

Restaurant menu

food_menu

Read-onlyIdempotent

Retrieve a single restaurant's full menu with each item's price, discount, packaging fee, and availability, so you can calculate the true cost per item before checkout.

Instructions

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

final_price = price - discount; packaging is added per item at checkout.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vendor_code": "<vendor_code>",
      "lat": "<lat>",
      "long": "<long>"
    },
    "name": "food_menu"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Delivery latitude.
`long`	Yes	Delivery longitude.
`limit`	No	Max items.
`query`	No	Title contains this.
`vendor_code`	Yes	Vendor code, e.g. '947evd'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.4.0Nov 7, 2026

changedInput schema / properties / lat / description

Previous value: -"Delivery point latitude."New value: +"Delivery latitude."

changedInput schema / properties / long / description

Previous value: -"Delivery point longitude."New value: +"Delivery longitude."

removedInput schema / properties / query / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / query / description

Previous value: -"Only items whose title contains this."New value: +"Title contains this."

addedInput schema / properties / query / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedInput schema / properties / vendor_code / description

Previous value: -"Vendor code, e.g. '947evd' (from food_search / food_restaurants)."New value: +"Vendor code, e.g. '947evd'."

Changed13 schema fields changedv0.2.0Oct 17, 2026

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

First observedv0.1.1Oct 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description goes beyond them by disclosing the return contents (price, discount, packaging fee, availability) and the price arithmetic used at checkout, which is real behavioral context an agent would otherwise have to discover by calling.

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, with the resource and returned fields front-loaded and the price formula isolated afterward. Every clause carries information; nothing is repeated from the schema or title.

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 must carry the return-value burden, and it does so reasonably by enumerating item fields and the final_price calculation. Minor gaps remain, such as whether pricing or availability varies by the supplied delivery coordinates and how limit/query affect the returned set.

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 vendor_code, lat, long, query, and limit are already documented with types, ranges, and patterns. The description adds no parameter-level meaning such as how query matching interacts with limit or why the delivery coordinates are required for a menu read.

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?

"Get one restaurant's menu" states a specific verb and resource, and the phrase "one restaurant's" scopes it to a single vendor, which separates it from multi-vendor siblings like food_search or food_restaurants. It does not name a sibling explicitly, so it falls just short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for viewing a known vendor's catalog after obtaining a vendor_code, but the description never says when to prefer it over food_search, food_find_cheapest, or food_meal_for_one. No exclusions or prerequisites are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.