Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rothys_product_recommendations

Retrieve recommended products for a Rothy's product handle by intent (related or complementary), with an optional limit up to 20.

Instructions

List Rothy's product recommendations. Returns recommended products for one Rothy's (https://www.rothys.com) product handle. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum products, defaults to 10 and supports up to 20
handleYesProduct handle
intentNoRecommendation intent. Allowed values: related, complementary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / intent / enum
      Added value: +[
+  "related",
+  "complementary"
+]
  2. 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 usefully discloses one behavioral trait — the storefront URL is fixed server-side, so no URL parameter is needed — and 'List...Returns' implies a read-only, non-mutating call. It does not describe pagination, ordering, or failure behavior when a handle is invalid.

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, front-loaded sentences with the core action first. There is mild redundancy between 'List Rothy's product recommendations' and 'Returns recommended products', but no filler or wasted length.

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

Completeness3/5

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

For a 3-parameter, no-annotation, no-output-schema tool, the description is adequate: it identifies the resource and the fixed-URL constraint. It does not describe what a recommendation record contains or how the 'related' vs 'complementary' intent changes results, which matters when no output schema exists to explain the return shape.

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 handle, limit (default 10, max 20), and the intent enum are fully documented in the schema. The description only reinforces that the call is anchored to a single product handle and adds no syntax or selection guidance beyond it — baseline 3.

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 ('List Rothy's product recommendations') and clarifies the anchor input ('recommended products for one Rothy's product handle'). It is distinguishable from generic list tools, but it never explicitly contrasts itself with the very similar rothys_product, rothys_products, or rothys_collections siblings.

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 when-to-use guidance and no alternatives. With ~18 sibling *_product_recommendations tools plus rothys_product/rothys_products in the same namespace, the agent gets no help deciding between fetching one product, listing products, or pulling recommendations.

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