Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rothys_search_suggest

Retrieve Rothy's predictive search suggestions, including products, collections, and queries, for any search term via Crawlora MCP.

Instructions

Get Rothy's search suggestions. Returns products, collections, and query suggestions from Rothy's's (https://www.rothys.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.2/5.0
Behavior3/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 adds one genuinely useful behavioral fact ('the storefront URL is fixed server-side', meaning no store parameter is needed) plus the shape of the response. However it omits auth needs, rate limits, and pagination behavior for a network-backed tool.

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 short sentences, front-loaded with the core purpose. Minor waste in 'Rothy's's' and the parenthetical URL, but overall tight and easy to scan.

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?

For a simple three-parameter suggest tool with no output schema and fully documented params, the description covers what it does and what it returns. It is complete enough to invoke correctly; only auth/limit context is absent.

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 schema fully documents q, limit, and types; baseline is 3. The description's enumeration of returned types (products, collections, query suggestions) loosely mirrors the 'types' allowed values but adds no new syntax or constraint detail 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?

States a specific verb and resource ('Get Rothy's search suggestions') and clarifies the return surface (products, collections, query suggestions from predictive search). It does not explicitly differentiate itself from the many sibling *_search_suggest tools, but for a store-scoped tool 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?

There is no when-to-use guidance, no mention of alternatives, and no prerequisites. The description says what it returns but never indicates when an agent should reach for this instead of rothys_products or rothys_collections. Usage is only inferred from the name.

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