Skip to main content
Glama

Compare products

compare_products
Read-onlyIdempotent

Compares 2 to 6 published products by name or ID and asks for clarification when a match is unclear. The compact answer includes daily amounts, rounded prices and applicable comparisons where available. Use detail "full" for the verified pack basis and detailed reference comparisons. The applicable comparison can vary with age and intake scope. Reference data only: it does not cover medication interactions, diagnosis or treatment decisions. Daily prices are rounded figures as published; they are not a basis for per-milligram or other derived costs.

Input Schema

NameRequiredDescriptionDefault
idsNoProduct ids, e.g. ["US:302778", "US:217710"].
detailNoCompact answer by default. Use full for the complete published record.compact
countryNoThe United States is the only market currently available.US
productsNoNames of the products to compare.
period_daysNoOptional days of consumption, calculated from verified pack and daily-use basis. This is not a whole-pack checkout price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, yet the description adds substantial behavior: it asks for clarification when a name match is unclear, reports that results can vary with age and intake scope, and warns that daily prices are rounded and unsuitable for per-milligram derivations. These are non-obvious traits an agent cannot infer from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five tight sentences, front-loaded with the core action and cardinality, followed by output shape, detail guidance, and caveats. Every sentence carries information, though the reference-data and rounding caveats could be consolidated into one scope sentence.

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 no output schema, the description correctly takes on the burden of describing the return payload (daily amounts, rounded prices, applicable comparisons) and its limitations. The remaining gap is the input contract: it never states that exactly one of ids or products should be supplied rather than both.

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 already 100%, so the baseline is 3, but the description adds real meaning beyond it: it explains what "full" detail unlocks, clarifies that period_days is not a whole-pack checkout price, and notes that the applicable comparison depends on age and intake scope. It does not address whether ids and products may be combined under the oneOf constraint.

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 opens with a specific verb and resource ("Compares 2 to 6 published products") and states both input modes (name or ID), so the agent knows exactly what the tool produces. It does not explicitly contrast itself with siblings like get_product or search_products, so it falls short of the top mark.

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 actionable selection guidance for the detail parameter ("Use detail \"full\" for the verified pack basis and detailed reference comparisons") and a clear scope exclusion ("does not cover medication interactions, diagnosis or treatment decisions"). It stops short of naming an alternative tool for single-product lookups or for the excluded use cases.

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