Skip to main content
Glama

Ramzii

Compare a shopping basket

compare_basket
Read-onlyIdempotent

Prices a whole shopping list at each Israeli supermarket chain's online store and ranks the chains: the total for each chain including its delivery fee, the cheapest chain, the items each chain is missing, the date of the prices, and a link that opens the basket on Ramzii. Example list: "חלב 3%\n2 לחם אחיד\nביצים L 12\nעגבניות 1 ק"ג".

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": {
      "list": "<list>"
    },
    "name": "compare_basket"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYesThe shopping list, one product per line, as the person wrote it, in Hebrew. Quantities may lead or follow (e.g. "2 חלב 3%", "עגבניות 1.5 ק"ג"). Up to 40 lines.

Output Schema

NameRequiredDescriptionDefault
open_urlYesA www.ramzii.co.il link that opens this answer.
data_dateYesIsraeli day (YYYY-MM-DD) of the oldest price in the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description then adds genuinely new behavior — that results are ranked per chain, include delivery fees, flag per-chain missing items, and carry a price date and a Ramzii deep link. It does not mention latency, cost, or how stale prices are tolerated, which keeps 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.

Conciseness4/5

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

One front-loaded sentence delivers purpose and complete return inventory, followed by a compact concrete example. It is dense but every clause earns its place; the only cost is that the primary sentence is long and reads as a comma-separated list of outputs rather than being chunked.

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 a rich annotation set, a fully documented single parameter, and an existing output schema, essentially everything an agent needs to decide and call correctly is present, including what a result means (ranked chains, delivery fee, missing items, price date, deep link) and how unmatched items surface. No material gap remains.

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?

There is a single parameter with 100% schema description coverage, and the schema already documents the one-per-line Hebrew format, lead/trail quantity variation, the 40-line cap, and a concrete example. The description restates the format expectations and adds a second example ('חלב 3%\n2 לחם אחיד...'), which is a useful illustration but largely duplicative of the schema — the baseline 3 for full coverage.

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?

The description states a specific verb and resource — it prices a whole shopping list across Israeli supermarket chains and ranks them — and enumerates the exact result contents (total with delivery fee, cheapest chain, missing items, price date, Ramzii link). It is unambiguous on its own, but it never positions itself against the sibling tools (match_list, product_prices, search_products), which a 5 would require.

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: the example list and the phrase 'prices a whole shopping list' make it clear this is for full-basket cost comparison rather than single-product lookups, but the description never says when to prefer it over product_prices or match_list. There are no exclusions, no prerequisites, and no guidance on whether to pre-resolve product names 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