Skip to main content
Glama

Compare products side by side

compare_products
Read-onlyIdempotent

Sets two to four products (product_ids from search_products, or deal.ai links) side by side: each one's rating and best current price from a store with when it was seen, their specifications aligned by name where they share them, each product's deal.ai page, and deal.ai's comparison page for a pair where there is one.

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": {
      "products": "<products>"
    },
    "name": "compare_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYesTwo to four products: product_ids from search_products, or deal.ai product links.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description only needed incremental context and does supply it: price freshness ("when it was seen"), that specs are aligned only where shared, and that the deal.ai comparison page exists only "for a pair where there is one." That conditional framing is genuinely useful, though error behavior for invalid ids is unaddressed.

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?

A single tight sentence with the action front-loaded and no filler. The nested clauses about ratings, prices, and aligned specs make it dense but every listed output earns its place; a light structural break would improve scannability.

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?

There is no output schema, so the description correctly carries the burden of explaining return contents and does so in detail, including conditional fields. The only real gap is failure modes for unrecognized ids or unavailability, which matters little for a read-only comparison tool.

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 single parameter already documents both accepted forms (product_id or https://deal.ai/p/... link) plus min/max items, so the description adds little beyond restating the source tool and the domain. Baseline 3 applies since the schema does the heavy lifting.

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?

The description uses a specific verb and resource ("Sets two to four products ... side by side") and enumerates exactly what the comparison produces, so an agent knows this is a multi-product comparison tool, not a lookup or search. It also implicitly distinguishes itself from search_products by naming that tool as the source of product_ids.

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

Usage Guidelines3/5

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

It gives useful input-provenance guidance (ids come from search_products, or deal.ai links) and states the 2-4 product constraint, which tells an agent when the tool is applicable. However, it never says when to prefer this over get_product_details or get_product_prices, nor what to do when a comparison isn't warranted.

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.