Skip to main content
Glama

Compare items

compare_items
Read-onlyIdempotent

Compare 1–25 supplied exact variants independently in one market. Each result has its own status and pagination. Does not select sellers, total a basket, or purchase. Each offer names its seller and observed_at; a null delivery cost or total is unknown, never zero. purchase_url is a Tallybuy link; Tallybuy may earn a commission when someone buys, at no extra cost to them. Say so when you give the link. Use list_offers instead for one variant.

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": {
      "market_id": "<market_id>",
      "currency": "<currency>",
      "destination_country": "<destination_country>",
      "items": "<items>"
    },
    "name": "compare_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
itemsYes
audienceNo
currencyYes
market_idYes
page_sizeNo
context_keyNoOptional; defaults to country:<destination_country>, the market's default context in which delivered totals are known. Leave empty unless you hold a different context key
destination_countryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnly, idempotent, non-destructive, closed-world), and the description still adds real behavioral context beyond them: per-result status and pagination, the rule that a null delivery cost or total means unknown rather than zero, and the commission-disclosure obligation attached to purchase_url. These are non-obvious operating facts an agent could not derive from the structured fields.

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?

Six short sentences, each carrying a distinct payload: scope, result shape, exclusions, null semantics, affiliate disclosure, and the sibling alternative. The most decision-relevant constraint (scope and variant count) is front-loaded, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values and the annotations cover safety, so those burdens are lifted. However, for a tool with 8 parameters, a nested item object, and 13% schema coverage, the description should say more about how the item list, cursors, and pagination interact; the mention that 'each result has its own status and pagination' raises the cursor question without answering it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13%, with 8 parameters and a 9-property nested item object, so the description is expected to carry the load. It contributes only the 1–25 item cap, which is genuinely absent from the schema, but leaves sort, page_size, audience, currency, market_id, destination_country, and item fields such as condition, quantity, merchant_id, availability, and cursor entirely unexplained.

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?

The description states a specific verb and resource ('Compare 1–25 supplied exact variants') and scopes it precisely to 'independently in one market'. It also draws the line against the closest sibling by naming list_offers for the single-variant case, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use (1–25 exact variants in one market) and explicit when-not ('Use list_offers instead for one variant'), plus negative scoping that rules out seller selection, basket totals, and purchase. Nothing about tool selection 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