Skip to main content
Glama

Search products and prices

search_products
Read-onlyIdempotent

Finds products in Ramzii's catalog of Israeli supermarket online stores and gives today's price of each at every chain that sells it, with the cheapest chain, the date of the prices and the product's page on Ramzii. Example queries: "במבה", "קפה נמס עלית".

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many products to return (default 5).
queryYesProduct words in Hebrew, e.g. "במבה", "קוטג' 5%", "שמן זית".

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.7/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 the safety profile is covered. The description adds useful behavior beyond that: results are aggregated across every chain selling the product, include the cheapest chain and a price date, and link back to Ramzii. It does not mention limits, pagination, or empty-result behavior, keeping it short of a 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?

The purpose and returned fields are front-loaded in a single dense sentence, followed by two concrete example queries that earn their place by clarifying input language and format. The first sentence is long but contains no filler.

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 present, the description does not need to specify return structure, yet it still summarizes the key outputs, which helps an agent judge relevance. For a two-parameter read-only search, the remaining gaps (no-result handling, why max 8, sibling routing) are minor rather than blocking.

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% for both parameters, so the schema already documents the Hebrew query string and the limit (default 5, max 8). The description reinforces the Hebrew-language expectation with real examples but adds no syntax, normalization, or matching-semantics detail beyond the schema, which is the baseline-3 case.

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 names a specific verb and resource ("Finds products in Ramzii's catalog of Israeli supermarket online stores") and enumerates what comes back: today's price per chain, cheapest chain, price date, and product page. It is clear what the tool does, but it never distinguishes itself from siblings like product_prices or compare_basket, so an agent cannot rule those out from this text alone.

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 through sample queries ("במבה", "קפה נמס עלית"), which show what good input looks like but not when to choose this tool over product_prices or compare_basket. There are no explicit exclusions, prerequisites, or fallback guidance for empty results.

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