Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modaoperandi_search

Search Moda Operandi products by gender and either query or category. Filter by designer, color, size, price, availability, or sale status; returns products and facet counts.

Instructions

Search Moda Operandi products. Searches or browses the Moda Operandi catalogue for one department, with gender (women or men) required and either q or category needed as well. Filter by designer, color, size, availability, price range or on_sale, and sort with sort. limit is 1 to 180 per page. Returns products plus facet counts and the total.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search
pageNo1-based page
sizeNoSize facet value
sortNoSort
colorNoColor facet value
limitNoResults per page
genderYesDepartment
on_saleNoSale items only
categoryNoCategory slug from modaoperandi-categories
designerNoDesigner slug from modaoperandi-designers
attributeNoAttribute facet value
price_maxNoMaximum price
price_minNoMinimum price
availabilityNoAvailability

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the required parameter combination, the valid pagination bound ('limit is 1 to 180 per page'), and the return shape ('products plus facet counts and the total'). It omits any auth, rate-limit, or error behavior, keeping 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.

Conciseness5/5

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

Four dense sentences, each earning its place: purpose, required inputs, filter/sort surface, and return shape, with the required-input constraint front-loaded. No filler or repetition.

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 output schema, the description correctly explains the return value (products, facet counts, total) and covers the filter/pagination surface across 14 parameters. It does not address how 'page' and 'limit' interact for pagination, a minor gap given the otherwise complete coverage.

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, but the description adds real semantics the schema lacks: the mandatory 'gender', the q-or-category requirement, and the 1-180 bound on 'limit'. It does not clarify facet-value sources beyond the schema's own hints, so it stays at 4.

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 Moda Operandi products') and immediately clarifies it can search or browse the catalogue for one department. It does not explicitly name sibling tools like modaoperandi_product or modaoperandi_categories to distinguish itself, so it stops short of a 5, but the verb+resource+scope is unambiguous.

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 concrete usage context: 'gender' is required and either 'q' or 'category' must also be supplied, which tells the agent exactly how to invoke it. It does not name an alternative tool or state when-not to use this one, so it is clear context without explicit 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