Skip to main content
Glama

marketbasketanalysis-mcp

score_cross_sell

Read-onlyIdempotent

Score the cross-sell strength (product affinity) between two specific products. Returns the confidence the merchant's real co-purchase data supports for the pair, or a clear 'no signal' result when there's no qualifying rule. Use this to validate a proposed pair before recommending it, or to answer 'is X a good cross-sell for Y?', 'how strong is the affinity between X and Y?', or 'how often are X and Y bought together?'.

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_a": "<product_a>",
      "product_b": "<product_b>"
    },
    "name": "score_cross_sell"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_aYesThe 'antecedent' product (the one the customer already has).
product_bYesThe 'consequent' product (the one being evaluated as a cross-sell).

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 cover readOnly, idempotent, non-destructive and closed-world, so the description's job is added context. It delivers that by disclosing the result semantics: a confidence value grounded in the merchant's real co-purchase data, plus an explicit 'no signal' outcome when no qualifying rule exists — a failure mode an agent would otherwise misread as an error.

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-loads the action in the first sentence, then the return behavior, then usage triggers. The three example phrasings run slightly long but function as routing 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 tool with no output schema, the description carries the necessary return-value burden by describing a confidence result versus a 'no signal' result. It could be marginally tighter about the form of the returned confidence (numeric scale, banding), which is the only remaining gap.

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% and the schema itself already defines product_a as the antecedent (owned) item and product_b as the consequent (candidate cross-sell), so the ordered/asymmetric nature of the pair is documented there. The description adds no further syntax, identifier format, or matching guidance beyond what the schema supplies, making the baseline 3 correct.

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 ('score the cross-sell strength / product affinity between two specific products') and scopes it to a single named pair, which clearly separates it from discovery-style siblings like get_opportunities or get_recommendations.

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?

Explicitly frames the use case as validating a proposed pair before recommending it and supplies concrete trigger questions ('is X a good cross-sell for Y?'). It stops short of naming an alternative tool or stating when-not to use it, so no exclusions are given.

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