Skip to main content
Glama

Find similar listings

similar_items
Read-onlyIdempotent

Find listings that look and read like a given one, to offer alternatives or comparisons. Pass a product id from search_catalog or get_item.

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": "similar_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
languageNoThe buyer's language: titles come back as whoppah.com shows them in it, and links open the listing's page in it.en
product_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "default": "en",
      +  "description": "The buyer's language: titles come back as whoppah.com shows them in it, and links open the listing's page in it.",
      +  "enum": [
      +    "en",
      +    "nl",
      +    "de",
      +    "fr",
      +    "es",
      +    "it"
      +  ],
      +  "title": "Language",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is fully covered. The description adds the useful detail that similarity is both visual ("look") and textual ("read"), but says nothing about result volume, ranking, or what happens when no similar items exist. Given the rich annotation set and an output schema, a 3 is appropriate.

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: the first states what the tool does, the second states the input dependency. Nothing is redundant and the core purpose is front-loaded.

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 annotations covering safety, a schema describing the language behavior, and an output schema handling returns, the description fills the main remaining gap: the provenance of the required id. Only the limit parameter's meaning is left without any coverage, a minor omission for a three-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description must compensate, and it does for the required parameter by specifying its origin (a product id from search_catalog or get_item) — context the bare "Product Id" string does not supply. The optional limit parameter remains entirely unaddressed in both schema and description, preventing a 5.

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?

"Find listings that look and read like a given one" names a specific verb and resource plus the similarity basis (visual and textual), which no sibling tool offers. It is clearly separable from search_catalog and get_item, which it positions as upstream id sources.

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?

It gives the concrete use case ("to offer alternatives or comparisons") and a prerequisite chain that tells the agent where product_id must come from (search_catalog or get_item). It stops short of an explicit when-not or an alternative-if-no-results path, which keeps it from a 5.

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