Skip to main content
Glama

Compare prices across sellers

compare_prices
Read-only

Who else sells this exact item, each priced for the same option — matched on Shopify catalog id or barcode, so a cheaper seller is a real match rather than a lookalike. Resellers are labelled and similar listings are kept apart from price matches. Pass variant_id (from get_product) for a multi-option product. Examples: "who else sells this exact Owala bottle", "is the official store actually cheaper".

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_url": "<product_url>"
    },
    "name": "compare_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
variant_idNoOption to price (variant_id from get_product)
product_urlYesA product_url from search_products

Output Schema

NameRequiredDescriptionDefault
lowestNo
variantNo
coverageYes
exhaustiveYes
candidate_limitNo
search_succeededNo
similar_listingsNo
same_item_sellersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / product_url / description
      Previous value: -"Shopify product URL (seller_url)"New value: +"A product_url from search_products"
  2. Changed9 schema fields changed
    • addedInput schema / properties / variant_id
      Added value: +{
      +  "description": "Option to price (variant_id from get_product)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / candidate_limit
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / coverage / enum
      Added value: +[
      +  "bounded_catalog_search",
      +  "incomplete_search_failed"
      +]
    • addedOutput schema / properties / exhaustive
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / lowest
      Added value: +{
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / same_item_sellers / items / properties
      Added value: +{
      +  "match": {
      +    "type": "string"
      +  },
      +  "price": {
      +    "type": [
      +      "object",
      +      "null"
      +    ]
      +  },
      +  "price_basis": {
      +    "enum": [
      +      "matched_variant",
      +      "unresolved_variant"
      +    ],
      +    "type": "string"
      +  },
      +  "seller": {
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / search_succeeded
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / variant
      Added value: +{
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "same_item_sellers"
      -]New value: +[
      +  "same_item_sellers",
      +  "coverage",
      +  "exhaustive"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / product_url / description
      Previous value: -"The seller_url of the item to price-check."New value: +"Shopify product URL (seller_url)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "coverage": {
      +      "type": "string"
      +    },
      +    "same_item_sellers": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "similar_listings": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "same_item_sellers"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), so the description's job is to add semantics — and it does: matching is on catalog id or barcode, resellers are labelled, and similar listings are deliberately kept apart from true price matches. That tells the agent how to interpret results, not just what the tool does. It stops short of describing pagination or coverage limits.

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?

Front-loaded with the core purpose, then matching semantics, then the parameter hint, then examples — a sensible ordering. The clause 'so a cheaper seller is a real match rather than a lookalike' is slight embellishment, but it does real work by explaining why the matching rule matters.

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?

An output schema exists, so return values need not be spelled out, and the description still covers what distinguishes price matches from similar listings. Combined with the readOnly annotations and fully documented parameters, an agent has what it needs to call this correctly. Minor gaps remain around result limits or what happens with a non-Shopify product_url.

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% and both parameter descriptions already name their source tools, so the schema carries most of the load and the baseline of 3 applies. The description adds a small amount of meaning by explaining that variant_id matters for multi-option products, but it does not explain behavior when variant_id is omitted for such a product.

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?

States a specific verb and resource ('Who else sells this exact item, each priced for the same option') and pins down the matching method — Shopify catalog id or barcode. It also separates itself from lookalike listings, so an agent can tell this apart from search_products or get_product without opening a schema.

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?

Gives concrete invocation conditions: pass variant_id '(from get_product) for a multi-option product', and the schema confirms product_url comes from search_products. Sample queries ('who else sells this exact Owala bottle', 'is the official store actually cheaper') make the intended use case concrete. It lacks an explicit when-not-to-use statement or named alternative to avoid, which keeps it just below 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