kazaplan-mcp

Overview Schema Source Related Servers Discussions Admin

Kz Search Catalog

kz_search_catalog

Search the local Leroy Merlin catalog by text, category, style, dimensions, or usage to find furniture and materials for a 3D home design.

Instructions

Recherche dans le catalogue Leroy Merlin local (plein texte FR, sans accents requis). kind : "model" (meubles/objets) ou "material" (revêtements). category : libellé ou code de menu (ex. "Baignoires", "SDB_BAIGNOIRES", "Canapés"). usage (matériaux) : "floor" ou "wall". style : Design, Essential, Natural, Industrial, Boheme, Neoclassic, Country. w = largeur (face avant), d = profondeur, h = hauteur, en cm ; price en € TTC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kz_search_catalog"
  }
}

Input Schema

Name	Required	Default
`kind`	No	model
`color`	No
`limit`	No
`max_d`	No
`max_h`	No
`max_w`	No
`query`	No
`style`	No
`usage`	No
`category`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses accent-insensitive full-text search over a local catalog and enumerates domain values for kind, usage, and style, but omits read-only nature, result-limit behavior (limit defaults to 15), pagination, and ordering semantics.

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 description is compact and front-loads the purpose before a parameter glossary. Minor waste appears in the trailing 'price en € TTC' line, which does not correspond to any schema parameter, and the w/d/h shorthand requires inference to the max_* fields.

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?

For a 10-parameter search tool with no annotations and no schema descriptions, the definition covers many domain-specific filters but is incomplete for the core query parameter, color, and limit. It also does not explain how the max dimension filters are applied, although the output schema covers return values.

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 0%, so the description must compensate. It adds valuable meaning for kind, category, usage, style, and dimension units, but leaves query, color, limit, and the max_w/max_d/max_h filter semantics undocumented; it also mentions price although no price parameter exists.

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 states a specific action: full-text search in the local Leroy Merlin catalog, with accent-insensitive French matching. It clearly distinguishes the kind values model (furniture/objects) and material (coverings), though it does not explicitly differentiate this from sibling kz_catalog_item.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as kz_catalog_item, nor any prerequisites or exclusions. The parameter hints imply catalog lookup, but the agent must infer the usage context.

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