Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

moncler_search

Search Moncler's product catalog by keyword for names, prices, images, variant IDs, live stock, sort options, and facets; filter and paginate results.

Instructions

Search Moncler products. Searches Moncler's product catalog by keyword. Returns product results (name, price, image, orderable color/size variant ids, and live stock level) plus the search index's own sort options and facets (gender, category, color, size, and others) with live per-option result counts. Narrow the same results with the filter param below.

Input Schema

NameRequiredDescriptionDefault
qYesSearch keyword
sortNoSort order
limitNoMax results to return
filterNoRepeatable, up to 10. Each value is \
offsetNoResult offset for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and delivers: it enumerates the returned fields (name, price, image, orderable variant ids, live stock level) and the facet payload with live counts. It omits auth requirements, rate limits, and pagination behavior, keeping it out of the top tier.

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?

Three sentences, front-loaded with purpose, then returns, then the filter affordance. The return enumeration is dense but each clause is informative; no filler sentences.

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?

Given five params, no annotations, and no output schema, the description covers what the tool does and what it returns, which is the critical gap. It leaves pagination/limit behavior and stock semantics unstated, but nothing essential for invoking the tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description still adds value by tying the filter param to narrowing 'the same results' and by clarifying that sort options come from the search index, information the terse schema descriptions (one of which is truncated) do not convey.

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 and resource ('Search Moncler products... by keyword') and clarifies it queries Moncler's product catalog, which is distinct from moncler_product (detail) and moncler_suggest (autocomplete). It does not explicitly name or contrast those siblings, so it stops short of the 5 tier.

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?

Usage is implied by the act of keyword search, and the description notes that results can be narrowed via the filter param, but it never states when to prefer this tool over moncler_product, moncler_category, or moncler_suggest, nor any exclusions.

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

Deploy Server

Other Tools