get_cross_sellsGiven the current product, return related products from the cross-sell graph and the recommended bundle.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_context | No | Optional: extra context about the buyer's stack or goals | |
| current_product | Yes | Product the buyer is currently considering or already owns |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must disclose all behavioral traits. It states the tool returns products and a bundle, suggesting a read operation, but does not confirm safety, permissions, or side effects. Sufficient but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence of 18 words, highly concise, and front-loaded with the core purpose. No unnecessary information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description does not explain the return format, such as whether it returns a list of products with details or just IDs. The tool is adequately described for a simple query, but leaves some gaps about output structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and both parameters have clear descriptions in the schema. The description does not add meaning beyond the schema, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns related products from the cross-sell graph and a recommended bundle given a current product. It distinguishes from siblings like get_recommendation by specifying cross-sell and bundle.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when the buyer has a current product, but does not explicitly state when to use this tool versus alternatives like search_products or get_recommendation. No exclusions or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of the commerce and affiliate ecosystem: comparison, checkout, affiliate info, cross-sells, free tier, MCP install, pricing, recommendation, trust score, registration, partnership, consultation, search, and vendor verification. No two tools have overlapping purposes; boundaries are clear.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., compare_products, get_affiliate_info, request_partnership). While the verbs vary, the structure is predictable and uniform, with no mixing of conventions.
14 tools is well-scoped for a commerce marketplace server covering product discovery, comparison, pricing, affiliate management, checkout, partnerships, and vendor verification. Each tool serves a clear purpose without bloat.
The tool set covers the full lifecycle from product discovery to checkout, including affiliate management and partnerships. Minor gaps exist, such as lacking a dedicated tool for retrieving detailed product information beyond search results, but agents can work around this.