Skip to main content
Glama

Ask Bestie Computers

Compare products

compare_products
Read-onlyIdempotent

Side-by-side popularity, trend and US price for 2 to 5 products, e.g. ["RTX 5070", "RX 9070 XT"].

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description adds real value by naming the returned dimensions (popularity, trend, US price), which matters because there is no output schema, but it leaves price currency, price recency and behavior for unknown product names undisclosed.

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 front-loaded sentence with no wasted words, plus a concrete example that costs little space and improves clarity. Nothing could be removed without losing information.

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 low-complexity, single-parameter, read-only tool with full schema coverage and rich annotations, the description supplies the main missing piece — what data comes back. Only edge-case behavior (unknown products, partial matches, price staleness) is left unstated, which is minor at this complexity.

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 description coverage is 100% and the single parameter is documented as "Product ids or names", so the baseline is 3. The description's example array ["RTX 5070", "RX 9070 XT"] usefully shows the expected string format, and the 2-5 range merely restates minItems/maxItems already in the schema.

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 states a specific operation (side-by-side comparison) on a specific resource (2 to 5 products) and names the dimensions compared: popularity, trend and US price. It is immediately distinguishable from siblings like get_product or trending because it operates on a set rather than a single item, though it never names an alternative 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 by the cardinality constraint ("2 to 5 products") — the agent can infer this is the tool for multi-product comparison rather than single lookups. However, there is no explicit when-to-use/when-not guidance, no mention of what to do with a single product, and no reference to the sibling tools that would handle that case.

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