Skip to main content
Glama

marketbasketanalysis-mcp

get_recommendations

Read-onlyIdempotent

For a given product, recommend the top complementary, frequently-bought-together products customers also bought, based on mined order-history association rules. This is the single-product cross-sell tool. Use this when the user asks 'what goes with X?', 'what should I bundle with X?', 'what do customers also buy with X?', 'recommend products to cross-sell with X', or similar single-product co-purchase questions. Works for all five platforms: Shopify, BigCommerce, WooCommerce, Magento, and OroCommerce.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>"
    },
    "name": "get_recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of recommendations to return. Default 3, max 6.
product_idYesProduct id, either the numeric storefront id (e.g. '8472918765') or the platform-specific GID/SKU. Both are accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond them: recommendations derive from mined order-history association rules and work uniformly across Shopify, BigCommerce, WooCommerce, Magento, and OroCommerce. It does not address what happens when no associations exist for a product.

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?

Front-loaded with the core purpose and mechanism before the usage triggers. The enumerated example queries are slightly repetitive but serve as intent-matching cues rather than filler.

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 two-parameter read-only lookup with no output schema, the definition covers what it returns conceptually (ranked complementary products from order history) and where it applies. Minor gap: it does not describe the shape of results (e.g., ranked list with scores) or behavior on thin order history.

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 coverage is 100%: product_id's accepted formats (numeric storefront id or GID/SKU) and limit's default/max are fully documented in the schema. The description adds no parameter-level guidance, 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 and resource — recommend complementary, frequently-bought-together products for a given product — and names the underlying mechanism (mined order-history association rules). The line 'This is the single-product cross-sell tool' scopes it clearly against cart-level siblings like get_bundle_for_cart and analyze_basket.

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 concrete trigger phrasings ('what goes with X?', 'what should I bundle with X?', 'what do customers also buy with X?') that map user intent directly to this tool. It signals the single-product scope but never explicitly names a sibling or states when-not to use this versus get_bundle_for_cart or analyze_basket.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources