Crawlora MCP

modaoperandi_search

Read-only

Search or browse Moda Operandi product result rows with catalog filters. Use modaoperandi_categories and modaoperandi_designers to discover filter values or modaoperandi_product for one product's full detail.

Input Schema

Name	Required	Description
`q`	No	Free-text search
`page`	No	1-based page
`size`	No	Size facet value
`sort`	No	Sort. Documented values: default, price_low_to_high, price_high_to_low, newest.
`color`	No	Color facet value
`limit`	No	Results per page
`gender`	Yes	Department. Documented values: women, men.
`on_sale`	No	Sale items only
`category`	No	Category slug from modaoperandi-categories
`designer`	No	Designer slug from modaoperandi-designers
`attribute`	No	Attribute facet value
`price_max`	No	Maximum price
`price_min`	No	Minimum price
`availability`	No	Availability. Documented values: available_now, preorder, trunkshow.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 7, 2026
- addedInput schema / properties / attribute / description
```
Added value: +"Attribute facet value"
```
- addedInput schema / properties / availability / description
```
Added value: +"Availability. Documented values: available_now, preorder, trunkshow."
```
- addedInput schema / properties / category / description
```
Added value: +"Category slug from modaoperandi-categories"
```
- addedInput schema / properties / color / description
```
Added value: +"Color facet value"
```
- addedInput schema / properties / designer / description
```
Added value: +"Designer slug from modaoperandi-designers"
```
- addedInput schema / properties / gender / description
```
Added value: +"Department. Documented values: women, men."
```
- addedInput schema / properties / limit / description
```
Added value: +"Results per page"
```
- addedInput schema / properties / on_sale / description
```
Added value: +"Sale items only"
```
- addedInput schema / properties / page / description
```
Added value: +"1-based page"
```
- addedInput schema / properties / price_max / description
```
Added value: +"Maximum price"
```
- addedInput schema / properties / price_min / description
```
Added value: +"Minimum price"
```
- addedInput schema / properties / q / description
```
Added value: +"Free-text search"
```
- addedInput schema / properties / size / description
```
Added value: +"Size facet value"
```
- addedInput schema / properties / sort / description
```
Added value: +"Sort. Documented values: default, price_low_to_high, price_high_to_low, newest."
```
First observedOct 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds that results are paginated 'result rows' rather than full records, but says nothing about pagination behavior, result caps, or auth needs beyond what annotations supply.

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?

Two tight sentences, front-loaded with purpose then routing. Every clause earns its place with no redundancy.

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 an output schema present, return values needn't be explained, and the sibling routing plus facet-filter framing covers the workflow. Minor gaps remain (pagination/limit defaults, the required gender param) but nothing critical for correct invocation.

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% (14 params, all documented with facet/documented-value hints), so the schema carries parameter meaning. The description only alludes generically to 'catalog filters' and adds no syntax or format detail beyond the schema.

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 ('Search or browse') and resource ('Moda Operandi product result rows') plus scope ('with catalog filters'). It explicitly contrasts the returned granularity ('result rows') with modaoperandi_product's 'full detail', so an agent can distinguish it from siblings without opening a schema.

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

Usage Guidelines5/5

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

Routes the agent to three named siblings by function: modaoperandi_categories and modaoperandi_designers to discover filter values, and modaoperandi_product for a single product's detail. This effectively tells the agent when this tool is and isn't the right choice.

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

All Crawlora MCP 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.