Skip to main content
Glama

Compare products side by side

em_compare
Read-onlyIdempotent

Compare 2–5 Emalls products by price, rating, and specs that differ to choose between models; shared specs are counted, then check offers for the winner.

Instructions

Compare 2-5 Emalls products: prices, rating and only the specs whose values differ.

Use it to choose between models. specs maps each differing spec to a value per product id (missing = no value); same counts shared specs. Then em_offers for the winner.

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_ids": "<product_ids>"
    },
    "name": "em_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idsYes2-5 product ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / product_ids / description
      Previous value: -"2 to 5 Emalls product ids from em_search or em_similar."New value: +"2-5 product ids."
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds genuinely useful behavior beyond them: the result shape (`specs` maps each differing spec to a value per product id, missing means no value, `same` counts shared specs), which matters because there is no output schema. It stops short of saying how prices/ratings are shaped or what happens with invalid or duplicate ids.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short segments, front-loaded with the capability and followed by the return shape and the next step. Every sentence carries information and nothing is redundant.

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 one-parameter, read-only comparison tool with no output schema, the description supplies the missing return-field semantics and a follow-up path, which is close to complete. Minor gaps remain around how price/rating values are represented and error behavior for invalid ids.

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 the 2-5 id constraint, so the description adds no syntax or format detail beyond it. Baseline 3 applies when the schema carries the parameter burden.

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 names a specific verb and resource ('Compare 2-5 Emalls products') and scopes the output to prices, rating, and only differing specs, which separates it from a single-product lookup. It does not explicitly contrast itself with siblings like em_product or em_similar, so a reader still has to infer that boundary.

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?

'Use it to choose between models' states the decision-making context, and 'Then em_offers for the winner' gives an explicit follow-up handoff to a named sibling. There is no when-not guidance (e.g., what to use for a single product or for non-differing full specs), which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.