Skip to main content
Glama

Compare products

compare_products
Read-onlyIdempotent

Side-by-side popularity, trend and US price for 2 to 5 products, e.g. ["Ruby Woo", "Pillow Talk"].

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
productsYesProduct ids or names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real context beyond them: the comparison returns three specific signals and that pricing is US-only, which is a meaningful scope constraint for interpreting results.

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?

A single sentence front-loads the return content, then the cardinality constraint, then a concrete example. Nothing is wasted and no reading past the first clause is needed to know what it does.

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 simple read tool with full annotation coverage and a one-parameter schema, the definition is nearly sufficient. The only gap is that with no output schema, the description does not indicate the result structure (e.g. per-product rows), though the compared metrics are named.

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 100% and the single parameter is already documented as 'Product ids or names'. The description adds a concrete worked example ('Ruby Woo', 'Pillow Talk') that demonstrates free-text product/shade names rather than opaque ids, which is genuine clarification of accepted input format.

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 operation (side-by-side comparison) and the exact resource (2 to 5 products), and clarifies the compared dimensions: popularity, trend and US price. That clearly separates it from single-product siblings such as get_product, 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?

Usage is implied rather than stated: comparing 2 to 5 products is the intended context, and the 2-5 bound effectively excludes single-product lookups. There is no explicit when-not or pointer to alternatives like get_product or get_ranking, so the agent must infer routing.

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