Tollkit

Get details for several products at once

compare_products

Read-only

Price the same product at several stores — up to 5 URLs in ONE call and ONE payment.

USE THIS WHENEVER YOU HAVE MORE THAN ONE URL. Comparing an item across stores, checking a short list, or refreshing a handful of tracked prices. It returns full details for each URL so YOU can compare them; it does not rank them or pick a winner. Through get_product_details that is one EIP-3009 signature, one settlement and one round trip PER URL; this is one of each for the whole set.

RETURNS one entry per URL in the order given, each with the same product and page objects get_product_details returns, plus ok/error so a single dead URL does not cost you the rest.

COST $0.04 flat for up to 5 URLs — cheaper per page than calling get_product_details 5 times.

BILLING, stated plainly: the price is flat, so a batch where only SOME URLs succeed is charged in full. A batch where NO url succeeds returns an error and is not charged. If you have one URL and are unsure it is live, get_product_details is the cheaper bet.

Duplicate URLs are removed and not billed twice.

When to use: You have 2-5 product page URLs, the same item at different stores or a short list. Use instead: get_product_details for a single URL. Returns: one entry per URL in order, each ok or with its error.

Input Schema

Name	Required	Description
`urls`	Yes	Up to 5 absolute https:// product page URLs. Duplicates are removed and not billed twice.
`payment`	No	Base64-encoded x402 payment payload. Omit on the first call to receive payment requirements.
`allow_redirect`	No	Applies to every URL. See get_product_details for what it does.

Output Schema

Name	Required	Description
`failed`	Yes
`status`	Yes
`billing`	Yes	The billing rule, restated on every response rather than only in the docs.
`results`	Yes
`requested`	Yes
`succeeded`	Yes
`settlement`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 20, 2026

addedOutput schema / properties / results / items / properties / provenance

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "declared": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "inferred": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "source": {
+          "enum": [
+            "json-ld",
+            "meta",
+            "json-ld+meta",
+            "none"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "source",
+        "declared",
+        "inferred"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Per-URL: which fields the merchant declared vs the model inferred."
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "url",
-  "ok",
-  "product",
-  "page",
-  "cached",
-  "cache_age_seconds",
-  "error",
-  "message"
-]New value: +[
+  "url",
+  "ok",
+  "product",
+  "page",
+  "provenance",
+  "cached",
+  "cache_age_seconds",
+  "error",
+  "message"
+]

AddedSep 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, and the description goes well beyond that: flat $0.04 cost, full charge on partial success, no charge when all URLs fail, duplicate de-duplication and non-billing, and the distinct payment mechanics (one EIP-3009 signature/settlement/round trip for the whole set vs one per URL). It also states it returns full per-URL data and does not rank or pick a winner.

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

Conciseness3/5

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

Front-loaded and scannable, but there is real duplication: the return format ('one entry per URL in order, each ok/error') is stated twice and the when-to-use guidance is repeated in a trailing block. The content is useful but would benefit from trimming.

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

Completeness5/5

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

An output schema exists, yet the description still covers cost, billing edge cases, ordering, and error tolerance for dead URLs. For a paid batch tool with these stakes, an agent has everything needed to invoke it correctly.

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% so the baseline is 3, but the description adds meaning the schema does not: a single payment payload covers the whole batch, and duplicates are removed before billing. allow_redirect is deferred to the sibling tool by both schema and description, which is a minor gap.

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 — pricing one product across several stores — with a hard scope of up to 5 URLs in one call and one payment. It explicitly distinguishes itself from get_product_details, so an agent can choose between them 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?

Gives an explicit trigger ('USE THIS WHENEVER YOU HAVE MORE THAN ONE URL'), enumerates the qualifying scenarios, and names the alternative plus its condition ('Use instead: get_product_details for a single URL'). Nothing 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.

All Tollkit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.