Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

moncler_category

List products in a Moncler category using its category_id from moncler-categories to get search-like results with facets and filtering.

Instructions

Browse a Moncler category. Lists products within one category. category_id must be a value returned by moncler-categories' own category_id field -- a closed set the upstream defines. Returns the same result and facet shape as moncler-search. Narrow the same results with the filter param below.

Input Schema

NameRequiredDescriptionDefault
sortNoSort order
limitNoMax results to return
filterNoRepeatable, up to 10. Each value is \
offsetNoResult offset for pagination
category_idYesCategory id, from moncler-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior3/5

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

No annotations, so the description carries the full behavioral burden. It usefully discloses that the return is the same result and facet shape as moncler-search and that category ids are a closed, upstream-defined set, but says nothing about pagination limits, rate limiting, or whether offset/limit have caps.

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?

Four short sentences, front-loaded with the core action, and each adds a distinct fact (scope, id provenance, return shape, filter). Slightly clipped phrasing ('filter param below') costs a little polish but not comprehension.

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?

With no annotations and no output schema, the description does the important work of anchoring the id source and promising parity with moncler-search's result/facet shape. The main residual gap is the under-specified filter parameter, which neither schema nor description fully explains.

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 the baseline is 3. The description reinforces category_id provenance (closed set from moncler-categories) and tells the agent filter narrows results, but the schema's filter description is truncated ('Each value is \'), and the description does not supply the missing filter value syntax.

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?

States a specific verb+resource ('Lists products within one category') and puts it in contrast with two siblings: moncler-categories (source of category_id) and moncler-search (same result/facet shape). An agent can distinguish this tool from its nearest siblings without opening any schema.

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?

Gives a clear prerequisite ('category_id must be a value returned by moncler-categories') and routes the agent to it for id discovery. It does not explicitly say when to prefer this over moncler-search (i.e. when you already know the category), so the selection rule is implied rather than stated.

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