Skip to main content
Glama

Compare products side by side

compare_products
Read-onlyIdempotent

Puts 2 to 4 verified products from the same category side by side and lists the spec fields where they differ. Each product keeps its own source URL and check date.

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
langNoLanguage of text fields (notes, labels, answers). One of: "en" (English), "zh-hant" (Traditional Chinese), "zh-hans" (Simplified Chinese). Default "en". Spec values and model numbers are the same in every language. Example: "zh-hant".en
categoryNoOptional. Limits each lookup to one category, for when a model number matches products in more than one. One of: "chargers", "power-banks", "usb-c-cables", "mini-pcs", "kvm-switches", "usb-c-docks", "ssds", "nas", "wireless-chargers", "monitors", "memory", "power-supplies", "cpu-coolers", "graphics-cards", "video-cables", "ethernet-cables", "pc-power-cables", "usb-cables". No default. Example: "power-banks".
productsYesRequired. A list of 2 to 4 products from the same category, each given as a slug, model number or words from its name (1 to 120 characters each). The same product cannot appear twice. Example: ["A2687", "A2340"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Optional. Limits each lookup to one category, for when a model number matches products in more than one. One of: \"chargers\", \"power-banks\", \"usb-c-cables\", \"mini-pcs\", \"kvm-switches\", \"usb-c-docks\", \"ssds\", \"nas\", \"wireless-chargers\", \"monitors\", \"memory\", \"power-supplies\", \"cpu-coolers\", \"graphics-cards\", \"video-cables\", \"ethernet-cables\", \"pc-power-cables\", \"usb-cables\". No default. Example: \"power-banks\"."
    • changedInput schema / properties / lang / description
      Previous value: -"Language for text fields: en, zh-hant (Traditional Chinese) or zh-hans (Simplified Chinese)."New value: +"Language of text fields (notes, labels, answers). One of: \"en\" (English), \"zh-hant\" (Traditional Chinese), \"zh-hans\" (Simplified Chinese). Default \"en\". Spec values and model numbers are the same in every language. Example: \"zh-hant\"."
    • changedInput schema / properties / products / description
      Previous value: -"Slugs, model numbers or names, for example [\"A2687\", \"CD372\"]."New value: +"Required. A list of 2 to 4 products from the same category, each given as a slug, model number or words from its name (1 to 120 characters each). The same product cannot appear twice. Example: [\"A2687\", \"A2340\"]."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds real value beyond that by disclosing the output shape (differing spec fields only) and that each product keeps its own source URL and check date. It does not say how category mismatches or unverifiable products are handled.

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?

Two tight sentences with no filler; the core operation is front-loaded and the output behavior follows. Nothing is wasted, though it could be slightly sharper by stating the return format before the provenance detail.

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?

With only three parameters, full schema coverage and no output schema, the description covers the essential shape: input constraints, what is compared, and what comes back. The remaining gap is edge-case behavior (mixed categories, unverified matches), which an agent might need before calling.

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 every parameter, enum and the 2-to-4 item bound is already documented. The description's '2 to 4' and 'same category' simply restate the schema's minItems/maxItems and the category field, adding no new syntax or semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('puts 2 to 4 verified products ... side by side') plus the key output behavior ('lists the spec fields where they differ'). That operation is clearly distinct from retrieval siblings like get_product or search_products, though no sibling is named explicitly.

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?

The 'same category' constraint and the 2-to-4 product bound imply when the tool applies, and the category parameter is framed in the schema as a disambiguator. There is no explicit statement of when to prefer this over get_product or find_same_product, so the guidance is implied rather than stated.

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