SIIL Ostomy Store

search_products

Read-onlyIdempotent

Search SIIL clothing by keyword, category, or price range.

Args:
    query: Search keywords (matches product name, SKU, description).
           A lone category word (swimwear, belts, underwear) browses that
           live slug instead of full-text. Examples: "swimwear", "belt black", "MB01720"
    category: Filter by English name or live Woo slug.
              Aliases: swimwear=banoen, belts=cinturon-siil-en,
              underwear=intimo-en, panties=panties, wraps=bandas-en,
              lingerie=bodies-en, protector=siil-protector-en, accessories
    min_price: Minimum price in EUR (e.g. 30.0)
    max_price: Maximum price in EUR (e.g. 100.0)
    limit: Number of results (max 50, default 20)

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`category`	No
`max_price`	No
`min_price`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety bar is low; the description adds real behavioral detail beyond them — the 50-result cap (default 20 is in the schema, the cap is not), the lone-category-word slug-browsing quirk, and the alias resolution table.

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?

Front-loaded one-line purpose followed by a compact Args block; every line carries information. The alias list is long but each entry maps a real user term to a required slug, so it earns its space.

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?

A 5-parameter search tool with no annotations gaps and an output schema, and the description covers all parameters plus result capping. Minor gaps remain: no statement of default behavior with an empty query, result ordering, or pagination beyond the limit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — parameters carry only titles and defaults — so the description carries the full burden and does it well: query matching fields and examples, category aliases mapped to live slugs, min/max price currency, and the max-50 limit that is absent from 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?

States a specific verb (search) and resource (SIIL clothing) plus the three axes of search: keyword, category, price range. That distinguishes it from get_product (single item), but it never explicitly distinguishes itself from the sibling search_org_products, leaving the agent to infer the difference.

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?

It explains how to search (lone category words browse a slug rather than full-text) but gives no guidance on when to choose this tool over get_product or search_org_products, nor what happens with an empty query. Usage is implied rather than directed.

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

All SIIL Ostomy 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?