Skip to main content
Glama

Ramzii

Match a shopping list to products

match_list
Read-onlyIdempotent

Matches each line of a Hebrew shopping list to a product in Ramzii's catalog: the product found for each line, the lines that need the person to choose between close options (with the options), the lines that were not recognised, the date of the catalog, and a link that opens the list on Ramzii. Example list: "קוטג' 5%\nבמבה\nשמן זית".

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": "match_list"
  }
}

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.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-open-world behavior, so the bar is lower. The description adds real context: it enumerates the outcome categories (matched, ambiguous with options, unrecognised), the catalog date, and a deep link back to Ramzii, which tells the agent what to expect from an ambiguous or failed match.

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 dense but well-ordered sentence front-loading the core action, followed by a short example. The enumeration of return values overlaps with the output schema, but the structure remains readable and waste is limited.

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 an output schema and full annotations present, the description needs only to frame intent and behavior; it does that plus the ambiguous/unrecognised distinction. Minor gap: no statement about what happens on partial or zero matches beyond naming the categories.

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%, so the single 'list' parameter is already fully documented, including quantity placement and the 40-line cap. The description repeats the Hebrew-only constraint and adds only a worked example, which is marginal value over the schema.

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 and resource: matching each line of a Hebrew shopping list to a catalog product. The line-by-line list semantics clearly differentiate it from single-query siblings like search_products and product_prices.

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?

The 'shopping list' framing implies when the tool applies (a whole list rather than a single query), but it never explicitly says when to prefer it over search_products or compare_basket, and gives no exclusions.

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