Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modaoperandi_search

Search Moda Operandi's public catalog by category, designer, color, size, price, and availability. Filter women's or men's fashion items by sale, sort, or page.

Instructions

Search Moda Operandi products. Searches or browses Moda Operandi's public catalog with category, designer, color, size, availability, price, sale, sort, and page filters.

Input Schema

TableJSON 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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'searches or browses', which implies a read operation but doesn't disclose return format, pagination behavior, result limits, or any side effects. It offers no behavioral details beyond the basic action.

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 a single sentence with no fluff, front-loaded with the main purpose. It efficiently lists key filter types. It is appropriately sized for a search tool, though it could benefit from a second sentence on usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 14 parameters, a required gender field, no output schema, and no annotations, the description is too thin. It doesn't mention that gender is required, how to obtain valid category/designer slugs, what the response looks like, or how pagination works. An agent would lack essential context to call this tool correctly.

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 lists a subset of filters (category, designer, color, size, availability, price, sale, sort, page) but omits others like q, gender, limit, and attribute. It adds a high-level summary but no new meaning beyond the schema.

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 clearly states it searches or browses Moda Operandi's public catalog with a specific set of filters. It identifies the resource (products) and the action (search/browse). It doesn't explicitly differentiate from siblings like modaoperandi_product or modaoperandi_categories, but the purpose 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 Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives. It doesn't mention that category and designer slugs should come from modaoperandi_categories and modaoperandi_designers, nor does it state when a user would prefer modaoperandi_product. Usage context is only implied by the name 'search'.

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