Maison Éclaire

Search Maison Éclaire products

search_products

Read-onlyIdempotent

Search Maison Éclaire's catalogue of handmade candles, gift packs, flower boxes, candle holders, snow globes, table decor, wedding favours and candle-making supplies (wax, wicks, fragrance oils, dyes, moulds, kits) sold online with delivery across Morocco. Use when the user is looking for candles, a candle gift, or candle-making supplies in Morocco. Always use image_url (or the Image: lines) from this tool for product photos; never use other images.

Input Schema

Name	Required	Description	Default
`lang`	No	Language of names, descriptions, labels and URLs: fr (default), en or ar	fr
`limit`	No
`query`	Yes	What the user is looking for, in any language ("bougie parfumée", "soy wax", "شمع"). A budget in it ("moins de 150 dh", "under 150 MAD") caps the price unless max_price is given
`category`	No	Only this category (ids from list_categories)
`max_price`	No	Maximum price in MAD; sold-out products are left out
`in_stock_only`	No	Leave out sold-out products

Output Schema

Name	Required	Description
`total`	Yes
`products`	Yes
`search_url`	Yes
`applied_max_price`	No	Maximum price in MAD applied to the results: max_price, or a budget written in the query

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / query / description

Previous value: -"What the user is looking for, in any language (\"bougie parfumée\", \"soy wax\", \"شمع\")"New value: +"What the user is looking for, in any language (\"bougie parfumée\", \"soy wax\", \"شمع\"). A budget in it (\"moins de 150 dh\", \"under 150 MAD\") caps the price unless max_price is given"

addedOutput schema / properties / applied_max_price

Added value: +{
+  "description": "Maximum price in MAD applied to the results: max_price, or a budget written in the query",
+  "type": "number"
+}

Changed2 schema fields changedOct 25, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

First observedOct 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare the tool is read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral guidance beyond that: it constrains product images to image_url or Image: lines and warns never to use other images. It does not discuss pagination or limit behavior, 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.

Conciseness4/5

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

The purpose and product scope are front-loaded, followed by a clear usage condition and an image-sourcing rule. The first sentence is a long enumeration, but the items are relevant to search semantics and the definition avoids unrelated information.

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?

An output schema exists, so return-value details are not needed in the description. Given annotations, 83% schema coverage, and a required query parameter, the description supplies adequate scope and usage context. It could be slightly stronger by explicitly relating this tool to get_product and list_categories.

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 83%, so the schema already documents query, lang, limit, category, max_price, and in_stock_only well. The description adds no parameter-specific meaning beyond what the schema provides; its image_url instruction is about output usage, not an input parameter.

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 gives a specific verb ('Search') and resource ('Maison Éclaire's catalogue') and enumerates the product types covered, so an agent can understand what it returns. It does not explicitly differentiate itself from siblings such as get_product or list_categories, which keeps it from a 5.

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 clearly states when to use the tool: when the user is looking for candles, a candle gift, or candle-making supplies in Morocco. It does not name when-not conditions or point to alternatives like get_product or list_categories, so it is clear but not fully routing.

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

All Maison Éclaire 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?