Aqua Flow store

Search products

search_products

Read-onlyIdempotent

Search the אקווה פלו catalog (Israel) for water filters, UV lamps, descaling kits and fridge filters. Use when the user names a device (Tami 4 Family, Primo, Bubble Bar, Edge, Electra bar, Eden Pure, LG or Samsung fridge) or a need. Returns name, price in ILS including VAT, stock and URL, and shows a product list view.

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

Name	Required	Description
`limit`	No	Maximum results
`query`	Yes	Keywords in Hebrew or English, e.g. "סנן תמי 4 פרימו" or "UV lamp Edge"
`category_id`	No	Optional category id from list_categories
`in_stock_only`	No	Return only products in stock

Output Schema

Name	Required	Description	Default
`query`	No
`total`	Yes
`products`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and repeatability are covered. The description adds a genuine behavioral detail not in the annotations — that it renders a product list view and prices are in ILS including VAT — but the rest of the return description is redundant because an output schema exists.

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?

Two sentences, front-loaded with the catalog scope and followed by the usage trigger; every clause carries information. The enumerated return fields duplicate the output schema and could be trimmed without loss.

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 four fully documented parameters, a complete annotation set and an output schema, the description supplies the missing domain framing and usage trigger, which is enough for correct invocation. It could go one step further and name the sibling to use when the user already knows the exact product.

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%, so query syntax, the Hebrew/English hint, category_id provenance and limit bounds are all already documented in the schema. The description only adds the idea that the query may be a device brand name or a need, which is marginal value on top of the structured fields.

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 (search the אקווה פלו catalog) and scopes it tightly to water filters, UV lamps, descaling kits and fridge filters, so the agent knows exactly what domain this covers. It does not explicitly contrast itself with siblings like get_product or compare_products, leaving that distinction to be inferred from the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete trigger condition: use when the user names a device (Tami 4 Family, Primo, Bubble Bar, Edge, Electra bar, Eden Pure, LG/Samsung fridge) or a need. That is strong positive guidance, but there is no when-not guidance or pointer to the alternatives (get_product for a known item, compare_products for evaluations).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Aqua Flow store tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?