Skip to main content
Glama

Suggest similar products

suggest_similar_products
Read-only

After optimize_delivery priced the wrong product, use this to show other things the shopper might have meant. Send their words in HEBREW (original line or the correction) and the rejected product_id so that SKU is dropped. Example: priced נקניקיות פרגיות, shopper said thigh cuts → query='פרגיות' or 'שוקיים', product_id=. Then call optimize_delivery again with the same list, that line pinned to the chosen product_id. Also answers 'is there a cheaper one?': every suggestion carries fromPrice, the lowest it goes for at any storefront delivering to this address, and normalizedUnitPrice, the same money per 100g/100ml/piece. Compare on normalizedUnitPrice, NOT on fromPrice: a smaller pack is cheaper to buy and usually dearer per gram, so a saving claimed on fromPrice alone is wrong whenever the pack sizes differ. Results come back cheapest per unit first, and rejected carries the same fields so the swap is directly comparable. fromPrice is a floor across storefronts, so quote it as 'from ₪X'; pricedAtStorefronts=1 means it is one shop's price rather than a market rate. Send city or address, or no price can be reported at all. Do not use this for a first-pass shopping list — call optimize_delivery once with every line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name in Hebrew or English (also accepts CBS locality codes). Aliases resolve to one place — e.g. 'הרצליה', 'Herzliya', and '6400' are the same filter. May be combined with location as a disambiguation hint.
nearNo'lat,lng' string, e.g. '32.078,34.774', to find stores near a point.
limitNoMax neighbours to return. Default 8.
queryNoWhat they meant, in Hebrew. Prefer the correction ('שוקיים') or the original line ('פרגיות'). A Latin brand name matches nothing. Required unless product_id is set.
locationNoFree-text neighborhood or address in Israel, e.g. 'נווה עמל, הרצליה'. Resolved to coordinates via cached Nominatim. Do not combine with near.
radius_kmNoSearch radius in km around the resolved point. Defaults to 10km when near or location is set. Ignored without a point.
product_idNoThe product_id optimize_delivery priced that the shopper rejected. Excluded from results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations (readOnlyHint=true, openWorldHint=true, destructiveHint=false) are consistent. The description adds substantial behavioral context: results sorted by cheapest per unit, 'rejected' field has same fields for comparison, fromPrice is a floor across storefronts, pricedAtStorefronts=1 meaning single shop price, and the requirement to send city/address for price reporting. No contradictions.

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?

Description is front-loaded with purpose and example, and each sentence adds value. However, it is fairly long (multiple paragraphs) and could be more structured (e.g., bullet points for the pricing rules). Still efficient given the complexity of the tool's behavior.

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?

With 7 parameters, no output schema, and only basic annotations, the description fully covers the tool's context: usage scenario, workflow steps, result interpretation, pricing caveats, and required parameters for price reporting. No significant gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). The description adds critical semantic constraints beyond the schema: the query must be in Hebrew (original line or correction), product_id must be the rejected one from optimize_delivery, and city or address is required for price reporting (conditional requirement not in schema). Also explains the meaning of pricedAtStorefronts. This extra value justifies a 4.

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: to suggest similar products when optimize_delivery priced the wrong product. It specifies the verb ('suggest similar') and the resource ('products'), and distinguishes itself from siblings by explicitly stating it is not for first-pass shopping lists, contrasting with optimize_delivery.

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?

Provides explicit when to use (after optimize_delivery wrong pricing), when not to use (not for first-pass lists), and includes an example workflow with a specific alternative ('Then call optimize_delivery again'). It also gives detailed guidance on interpreting results (compare normalizedUnitPrice, not fromPrice).

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