XFish Horgász Webáruház

search_products

Termékkereső az XFish.hu horgász webáruházban. Keresés szöveg, kategória, gyártó, márka, ár és készlet alapján. Magyar és angol keresés is működik.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	Rendezés: relevance=releváns, price_asc=legolcsóbb, price_desc=legdrágább, name_asc=névsor	relevance
`brand`	No	Márkanév szűrő (pl: "Shimano", "Daiwa", "Fox"). Pontos gyártóra szűr. Ha a query tartalmazza a márkát, az automatikusan felismeri.
`limit`	No	Találatok száma (1-50, alapértelmezett: 10)
`query`	No	Keresőkifejezés — a termék típusa (pl: "feeder bot", "bojli 20mm", "pergető orsó"). Ha a brand-et is megadod, a query csak a típust tartalmazza.
`max_price`	No	Maximum bruttó ár (Ft)
`min_price`	No	Minimum bruttó ár (Ft)
`webshop_id`	No	Bolt ID: 0=Horgász, 1=Játék, 2=Kisállat, 3=Barkács (alapértelmezett: 0)
`category_id`	No	Kategória ID szűrés (a get_categories tool-ból kapott ID)
`in_stock_only`	No	Csak raktáron lévő termékek (alapértelmezett: igen)
`manufacturer_id`	No	Gyártó ID szűrés (a get_manufacturers tool-ból kapott ID)

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedMay 26, 2026

addedInput schema / properties / brand

Added value: +{
+  "description": "Márkanév szűrő (pl: \"Shimano\", \"Daiwa\", \"Fox\"). Pontos gyártóra szűr. Ha a query tartalmazza a márkát, az automatikusan felismeri.",
+  "type": "string"
+}

addedInput schema / properties / in_stock_only

Added value: +{
+  "default": true,
+  "description": "Csak raktáron lévő termékek (alapértelmezett: igen)",
+  "type": "boolean"
+}

addedInput schema / properties / limit / default
```
Added value: +10
```

changedInput schema / properties / limit / description

Previous value: -"Találatok száma (max 50, alapértelmezett: 10)"New value: +"Találatok száma (1-50, alapértelmezett: 10)"

addedInput schema / properties / limit / maximum
```
Added value: +50
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / manufacturer_id / description

Previous value: -"Gyártó ID szűrés"New value: +"Gyártó ID szűrés (a get_manufacturers tool-ból kapott ID)"

addedInput schema / properties / max_price / minimum
```
Added value: +0
```
addedInput schema / properties / min_price / minimum
```
Added value: +0
```
addedInput schema / properties / query / default
```
Added value: +""
```

changedInput schema / properties / query / description

Previous value: -"Keresőkifejezés (pl: \"shimano feeder bot\", \"bojli 20mm\", \"pontyozó orsó\")"New value: +"Keresőkifejezés — a termék típusa (pl: \"feeder bot\", \"bojli 20mm\", \"pergető orsó\"). Ha a brand-et is megadod, a query csak a típust tartalmazza."

addedInput schema / properties / sort

Added value: +{
+  "default": "relevance",
+  "description": "Rendezés: relevance=releváns, price_asc=legolcsóbb, price_desc=legdrágább, name_asc=névsor",
+  "enum": [
+    "relevance",
+    "price_asc",
+    "price_desc",
+    "name_asc"
+  ],
+  "type": "string"
+}

addedInput schema / properties / webshop_id

Added value: +{
+  "default": 0,
+  "description": "Bolt ID: 0=Horgász, 1=Játék, 2=Kisállat, 3=Barkács (alapértelmezett: 0)",
+  "enum": [
+    0,
+    1,
+    2,
+    3
+  ],
+  "type": "integer"
+}

First observedMar 25, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It mentions Hungarian and English search support, but does not disclose behavioral traits like authentication needs, rate limits, data freshness, or return format. The description adds minimal behavioral context beyond what is obvious from the name and schema.

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?

The description is two short sentences, front-loading the tool's purpose and key search dimensions. Every word is useful; no redundancy. Highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters and no output schema, the description is clear on search dimensions but omits expected return format (e.g., product list with fields). It does not address pagination beyond the limit parameter. It references category and manufacturer IDs from sibling tools in schema, but not in description. Adequate but incomplete for a fully informed agent.

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 baseline is 3. The description adds a multilingual capability note not present in schema, but otherwise does not significantly enhance parameter meaning beyond what schema already provides.

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?

The description clearly states it's a product search tool for the XFish.hu fishing webshop and lists the search criteria (text, category, manufacturer, brand, price, stock). It distinguishes from sibling tools (get_categories, get_manufacturers, get_product_details) by its search focus.

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 description implies usage for searching products but does not explicitly state when to use this tool vs alternatives. It mentions category and manufacturer IDs referring to other tools in schema descriptions, but no explicit 'when-not-to-use' or alternatives in the main description.

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

All XFish Horgász Webáruház 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?