Skip to main content
Glama
Sign In
snapp-mcp

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Meals for one

food_meal_for_one
Read-onlyIdempotent

Find single-person meals under 299k Toman with free delivery, sorted cheapest first. Check the minimum order—a low-cost meal may not fill the basket minimum.

Instructions

List single-person meals (at most 299k Toman, free delivery), cheapest first.

Use for "cheap meal for one". Check min_order: a cheap meal may not reach the minimum basket.

Input Schema

NameRequiredDescriptionDefault
latYesDelivery point latitude.
longYesDelivery point longitude.
limitNoMax meals.
max_priceNoMax final price, Toman.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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: -30New value: +15
    • changedInput schema / properties / limit / description
      Previous value: -"Max meals to return."New value: +"Max meals."
    • 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 / max_price / description
      Previous value: -"Only meals at or under this final price, Toman."New value: +"Max final price, Toman."
    • removedInput schema / properties / max_price / title
      Removed value: -"Max Price"
    • removedInput schema / title
      Removed value: -"food_meal_for_oneArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "food_meal_for_oneDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.1

TDQS

A4/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 structurally. The description adds real behavioral context beyond that: result ordering (cheapest first), a hard price ceiling, free-delivery requirement, and the warning that a cheap meal may fail the minimum basket — a genuinely useful operational caveat. Return format/pagination is not described, keeping it below 5.

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, zero filler, with the tool's scope and constraints front-loaded and the caveat placed last as an actionable warning. Every clause carries information an agent can act on.

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 is responsible for signaling the shape of results; it does so via 'cheapest first' and the price/delivery constraints. Four parameters are fully covered by the schema, and the min_order caveat closes the main operational gap, though the absence of any note on result limits or empty results is a minor shortfall.

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 coverage is 100%, with lat/long bounds, limit default, and max_price all documented in-schema, so the baseline is 3. The description's 299k price ceiling and cheapest-first ordering give indirect meaning to max_price and the result ordering but add no syntax or format detail beyond what the schema already carries.

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 precise verb+resource ('List single-person meals') with concrete constraints: price ceiling of 299k Toman, free delivery, and cheapest-first ordering. It distinguishes itself from generic siblings like food_search by the single-person/cheap scope, though it never names the closest alternative (e.g. food_find_cheapest) so the differentiation is inferential rather than explicit.

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 a direct trigger phrase ('Use for "cheap meal for one"') and adds a practical prerequisite caveat about checking min_order before committing. It does not state when NOT to use it or name sibling alternatives, so it stops short of the top tier.

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