Skip to main content
Glama

SuperMCP

by io.github.nitaiaharoni1
OverviewDiscussionsAdmin

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

TableJSON 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.5/5.0
Behavior5/5

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

The annotations already declare readOnly and openWorld hints, but the description adds significant behavioral context beyond that. It explains that the tool does not price a basket, describes the meaning of catalogVisibility and confidence fields, and cautions against recommending based solely on delivery fees. This provides deep transparency about the tool's behavior and limitations, going well beyond the annotations.

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

Conciseness3/5

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

The description is verbose and somewhat redundant. It repeats the pattern for catalogSize, notesRef, and includes the full parameter descriptions again. While each part adds some value, the repetition with the schema and the long-winded explanations (e.g., 'one where we hold a few hundred items cannot fill a normal basket') make it less concise than necessary.

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?

Since there is no output schema, the description compensates by explaining what each returned entry contains (deliveryTerms.confidence, verifiedAt, catalogSize, catalogVisibility) and what those fields mean. It also covers edge cases like missing chains and the use of include_unavailable. The description is complete for understanding the tool's behavior and output without requiring external knowledge.

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% and the description repeats the exact same parameter descriptions as in the schema. It does not add any new meaning or examples beyond what's already provided. Since coverage is high, the baseline is 3, and there is no extra semantic enrichment.

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?

The description clearly states the tool's purpose: it lists storefronts that deliver to a given address, with delivery terms like fees and minimum orders. It also distinguishes it from the optimize_delivery tool, which is used for pricing baskets. This is a specific verb + resource with clear differentiation from siblings.

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?

The description explicitly says 'Use for who delivers to me?' and contrasts with 'what will my shopping cost delivered?' for optimize_delivery. It also advises to use optimize_delivery before recommending based on fees alone. This gives explicit when-to-use and when-not-to-use guidance, exceeding simple context.

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

All SuperMCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources