Skip to main content
Glama

Similar products

em_similar
Read-onlyIdempotent

Lists products Emalls considers similar to a given product, showing lowest price and shop count so you can offer alternatives.

Instructions

List products Emalls shows as similar to one product, with lowest price and shop count.

Use it to offer alternatives. Loosely related (not always the same class): check with em_compare.

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_id": "<product_id>"
    },
    "name": "em_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
limitNoMax products.
product_idYesArgument is `product_id` (not `id`): the `id` of an em_search result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.1
    • changedInput schema / properties / product_id / description
      Previous value: -"Product id from em_search."New value: +"Argument is `product_id` (not `id`): the `id` of an em_search result."
  2. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max products to return (1-40)."New value: +"Max products."
    • changedInput schema / properties / page / description
      Previous value: -"Page number of the similar list, 1 is the first."New value: +"Page number."
    • changedInput schema / properties / product_id / description
      Previous value: -"Emalls product id from em_search, e.g. 26506037."New value: +"Product id from em_search."
  3. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real context beyond them: each result carries lowest price and shop count, and the similarity relation is flagged as loose and not always the same product class — a caveat an agent needs before presenting results as alternatives.

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 sentences, front-loaded with the operation and its output fields, then the usage/alternative guidance. No redundant restatement of name or annotations.

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 read-only list tool with a fully documented 3-parameter schema and no output schema, the description covers what is returned and how strict the relation is. Minor gaps remain around result count/pagination behavior, but nothing that would cause a misinvocation.

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 schema itself explains that product_id is the `id` of an em_search result rather than `id`. The description only says "similar to one product" and adds no paging or limit semantics beyond what the schema documents, so 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 and resource: list products Emalls deems similar to one product, and it names the payload (lowest price and shop count). The final sentence distinguishes it from em_compare by scope of relatedness, so an agent can pick between them without opening schemas.

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 offer alternatives" gives a clear use case, and "Loosely related (not always the same class): check with em_compare" routes the agent to a sibling when the strictness matters. It stops short of explicit when-not-to-use conditions or prerequisites, so it is not a full 5.

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