Aqua Flow guides

Search guides

search_guides

Read-onlyIdempotent

Search the store guides, articles and policy pages (Hebrew). Use when the user asks how to choose, replace or maintain a water filter, UV lamp or descaling kit, or asks about shipping, returns or warranty. Returns titles, excerpts and URLs; follow with get_guide for the full text.

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_guides"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum results
`query`	Yes	Question or keywords in Hebrew or English, e.g. "החלפת סנן תמי 4"

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered. The description adds genuinely new context beyond them: the corpus is Hebrew-language store content, results are titles/excerpts/URLs rather than full documents, and get_guide is the path to full text. It stops short of saying anything about ranking or why results might be empty, which keeps it from 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.

Conciseness5/5

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

Three tight sentences: what is searched, when to use it, and what happens next. The follow-up routing instruction is packed into the final sentence rather than a separate paragraph, and nothing is repeated from the schema.

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 an output schema present and annotations covering the safety profile, the description's only remaining obligations are purpose, trigger conditions and next step, all of which are present. Nothing an agent needs in order to call this correctly and then act on the results is missing.

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 query minLength and the Hebrew/English example plus limit's 1-10 range are already documented in the schema. The description only adds that the corpus itself is Hebrew, which is a mild hint about query language. Baseline 3 is appropriate when the schema carries the parameter detail.

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 (search) and resource (store guides, articles, policy pages) and flags the content language as Hebrew. It also distinguishes itself from get_guide by describing that tool as the follow-up for full text, so an agent can pick between them without inspecting either schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use triggers: questions about choosing, replacing or maintaining a water filter, UV lamp or descaling kit, plus shipping, returns and warranty topics. It also names the natural next tool (get_guide) for full text, which is the only routing decision this tool creates.

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

All Aqua Flow guides 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?