Skip to main content
Glama

List storefronts that deliver here

list_delivery_options
Read-only

Which Israeli online supermarkets deliver to an address, with each one's delivery fee, minimum order, free-delivery threshold and whether it offers click-and-collect — without pricing a basket. Use for 'who delivers to me?'. For 'what will my shopping cost delivered?', use optimize_delivery instead. Every entry carries deliveryTerms.confidence and verifiedAt; quote a fee only when it is verified or reported, and say the fee is unknown otherwise. Every entry also carries catalogSize (priced items we hold) and catalogVisibility. catalogVisibility 'partial_index' means WE cannot see the whole shop: that storefront's prices are read off a website that cannot be paged, so catalogSize is the part we indexed and says nothing about how much the retailer stocks. 'full_catalogue' means the count is the retailer's complete published price file. Never recommend a storefront on its delivery fee alone: one where we hold a few hundred items cannot fill a normal basket, so price the basket with optimize_delivery before naming a winner. An entry carrying notesRef instead of notes shares its terms with other storefronts: read the text from sharedNotes[notesRef]. Marketplace terms are written once per chain and held per venue, so they would otherwise repeat verbatim on every branch.

Input Schema

NameRequiredDescriptionDefault
cityNoCity name in Hebrew or English. Enough for chains that publish a settlement list, not enough for a storefront whose area is a polygon or a depot radius.
nearNo'lat,lng' string, e.g. '32.078,34.774'. Do not combine with address.
chainNoFilter to one chain, by its name as it appears in chainName (שופרסל) or by its legal barcode id. A value matching neither returns no options, which is not the same answer as nobody delivering here: omit it to see every storefront.
addressNoDelivery address in Israel, free text, e.g. 'מנדלסון 1, תל אביב'. Preferred: some storefronts publish a service area that only a street address can be tested against.
include_unavailableNoAlso return storefronts that do NOT serve this address, each with a reason. Useful for explaining why a well-known chain is missing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / city / minLength
      Added value: +1
    • addedInput schema / properties / near / minLength
      Added value: +3
  2. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain id (the chain's legal barcode id) to filter by."New value: +"Filter to one chain, by its name as it appears in chainName (שופרסל) or by its legal barcode id. A value matching neither returns no options, which is not the same answer as nobody delivering here: omit it to see every storefront."
  3. Changed2 schema fields changed
    • addedInput schema / properties / city / maxLength
      Added value: +100
    • addedInput schema / properties / near / maxLength
      Added value: +100
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), but the description adds substantial behavior the annotations do not: confidence/verifiedAt gating on quoted fees, the meaning of catalogVisibility 'partial_index' vs 'full_catalogue', notesRef/sharedNotes indirection, and the chain-level deduplication of venue terms. This is exactly the extra context the low annotation bar rewards.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The routing rule and the fee-confidence caveat are front-loaded ahead of the data-model explanation, which is good ordering. The description is dense and long, but nearly every sentence carries a distinct operational instruction rather than filler.

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?

There is no output schema, so the description must carry return-value semantics — and it does, documenting confidence, verifiedAt, catalogSize, catalogVisibility, notes/notesRef and sharedNotes. Combined with the safety annotations, an agent has everything needed to call and interpret this 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 each parameter already explains its own tradeoffs (city limitation for polygon areas, 'do not combine with address', chain filter returning no options). The description adds nothing parameter-specific, so the baseline of 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+resource ('Which Israeli online supermarkets deliver to an address') and enumerates exactly what each entry carries (fee, minimum order, free-delivery threshold, click-and-collect), while explicitly noting it does NOT price a basket. It is cleanly distinguishable from optimize_delivery, which is named directly.

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

Usage Guidelines5/5

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

Gives an explicit trigger phrase ('who delivers to me?') and an explicit routing rule for the sibling: 'For what will my shopping cost delivered?, use optimize_delivery instead.' It goes further by warning never to recommend on fee alone and directing the agent to price the basket with optimize_delivery first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources