Skip to main content
Glama

marketbasketanalysis-mcp

get_opportunities

Read-onlyIdempotent

List the merchant's ranked bundle / cross-sell opportunities mined from order history, with support / confidence / lift / revenue-weighted score. Use this when a merchant asks 'what are my top opportunities?', 'show me the best bundles I haven't published yet', or 'what should I prioritize?'. Read-only. Pair with explain_opportunity for the evidence behind a specific one. Merchant-ops surface: BigCommerce today; on other platforms merchants manage this from the admin, and the tool returns a clear not-available message.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax opportunities to return. Default 10, max 50.
statusNoFilter by opportunity status. Defaults to 'proposed' (untriaged).proposed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered; the description adds genuinely new behavior: the BigCommerce-only availability gate and the graceful not-available response on other platforms. It does not say what an empty result looks like or how ranking ties are broken, which keeps it below a 5.

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 verb and resource, then triggers, then the sibling pairing, then platform caveat — a sensible ordering. The platform-availability sentence is long and slightly buries an operational constraint at the end, but every sentence carries information an agent needs.

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

Completeness5/5

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

No output schema exists, so the description compensates by naming the returned ranking fields. Combined with trigger examples, the sibling handoff, and the platform limitation, an agent can decide to call this and predict the response shape without further context.

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 both parameters (limit with default 10/max 50, and status enum defaulting to 'proposed') are already fully documented in structured data. The description only hints at the status dimension via 'bundles I haven't published yet', adding no syntax or default detail beyond the schema — 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 ('ranked bundle / cross-sell opportunities mined from order history') and names the exact fields returned (support, confidence, lift, revenue-weighted score). The 'Pair with explain_opportunity' line separates it from the sibling that digs into one opportunity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger phrasings ('what are my top opportunities?', 'best bundles I haven't published yet', 'what should I prioritize?') plus an explicit alternative (explain_opportunity) for the evidence-drilldown case. It also states platform gating: works on BigCommerce today, returns a clear not-available message elsewhere.

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