Skip to main content
Glama

Similar products

get_similar_products
Read-onlyIdempotent

Get products similar to a given CacheBy product (vector similarity). Pass a product id from search_products results.

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": {
      "productId": "<productId>"
    },
    "name": "get_similar_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
productIdYesProduct id (UUID) from search_products results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered elsewhere. The description adds only the behind-the-scenes detail that matching is done via vector similarity, plus the id provenance constraint; it says nothing about result ordering, ranking, or behavior when the product has no neighbors.

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 action and the mechanism, with the id-source constraint placed where the caller will look for it. Nothing is padded or repeated.

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 two-parameter, fully annotated, read-only lookup with no output schema, this is nearly sufficient: you know what it does, what to feed it, and that it is safe. The only real gap is disambiguating 'similar' from the sibling 'substitutes', which an agent can't resolve from this text.

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%, so both parameters are already documented, including the limit default and maximum. The description's only parameter statement ('Pass a product id from search_products results') duplicates the schema's own productId text, so it adds no meaning beyond structured data.

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 ('Get products similar to a given CacheBy product') and even names the mechanism (vector similarity), which is real information. It stops short of differentiating itself from the sibling get_substitutes, which sounds adjacent, so an agent must guess which one applies.

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 states a prerequisite ('Pass a product id from search_products results'), implying you must first run search_products, which is useful usage context. There is no explicit when/when-not guidance and no mention of get_substitutes as an alternative, so selection against siblings is left to inference.

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