Skip to main content
Glama

GELATO.cz

Search products

search_products
Read-only

Search the e-shop catalog by product name or EAN code. Public — no authentication needed. Every product carries the EAN, brand, pack size with its unit (kg for goods sold by weight, ks for goods sold by the piece) and the resulting price_per_unit, plus weight_kg. Prices are EXCLUDING VAT — price_vat_included is false and vat_rate gives the rate in percent. The exact stock quantity is returned only to authenticated customers; anonymous callers get in_stock as a yes/no. Authenticated customers get prices that include their personal discount.

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
limitNoMax results, default 10
queryYesSearch phrase or EAN code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses a lot: anonymous vs authenticated response differences (yes/no in_stock vs exact quantity), personal discount affecting returned prices, and VAT semantics including price_vat_included=false and vat_rate in percent. These are exactly the behavioral traits an agent needs to interpret results correctly and are not available in any structured field.

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?

Purpose and access model are front-loaded in the first two sentences, followed by a dense but useful block on returned fields and pricing. It is longer than typical, yet each clause about units, VAT, and stock visibility carries information an agent would otherwise guess wrong.

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 no output schema, the description compensates by enumerating the return fields (EAN, brand, pack size with unit, price_per_unit, weight_kg) and explaining VAT and stock visibility. For a two-parameter read-only search this covers everything needed to call and interpret it.

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 both query and limit are already documented in the schema, and the description only restates that the query may be a name or an EAN code. The limit parameter and its default are not mentioned in the description at all, so no meaning is added beyond the schema.

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 first sentence gives a concrete verb and resource — "Search the e-shop catalog" — and narrows the lookup keys to product name or EAN code. It is clear enough to distinguish a catalog search from cart/order tools, though it never explicitly contrasts itself with the product-detail sibling.

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 implied rather than stated: the agent learns it can search by name or EAN and that no authentication is required. There is no explicit when-to-use/when-not guidance or routing toward a single-product lookup for a known identifier, so the agent must infer the boundary.

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