Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rothys_product_recommendations

Fetch Rothy's product recommendations for a handle by resolving it to a Shopify product id, returning related or complementary items with limit and intent options.

Instructions

List Rothy's product recommendations. Returns normalized recommended products for one Rothy's (https://www.rothys.com) product handle. The route handle is resolved to a Shopify product id before fetching recommendations. The storefront URL is fixed server-side.

Input Schema

TableJSON 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

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that results are normalized, the handle resolves to a Shopify product id, and the storefront URL is fixed server-side. However, it does not describe the output shape, pagination, or any side-effect profile, leaving notable gaps for a tool with no annotation safety hints.

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?

Three tightly worded sentences with the purpose front-loaded. Each subsequent sentence adds a distinct useful fact (normalization, Shopify id resolution, fixed storefront URL) with no filler or redundancy.

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?

Adequate for a straightforward recommendation endpoint whose parameters are fully documented. But with no output schema and no guidance on how to obtain a handle or what normalized output contains, an agent is left with minor but real gaps in predicting return values and chaining with sibling tools.

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 already documents handle, limit, and intent with their constraints. The description adds no parametric meaning beyond the handle-to-id resolution note, so the baseline 3 applies.

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 ('List') and resource ('Rothy's product recommendations') scoped to one product handle. This clearly differentiates it from siblings like rothys_product (single product details) and rothys_products (all products). An agent can tell what it does without opening the schema.

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 clear context: the tool takes one product handle and returns normalized recommendations, implying the need to first obtain a handle. It does not explicitly name alternatives or list when-not-to-use scenarios, but the context is sufficient for correct selection in most cases.

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