Tollkit Extract

Get details for several products at once

compare_products

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.15 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.

Input Schema

TableJSON 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

TableJSON 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.8/5.0

Behavior5/5

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

With no annotations, the description carries the full disclosure burden, and it does so thoroughly: it discloses one-signature/one-payment mechanics, flat $0.15 pricing, partial-success billing, no-charge on complete failure, duplicate removal, and non-ranking behavior. It also explains that a single dead URL does not fail the whole batch, which is exactly the kind of behavioral trait an agent needs to expect.

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?

The description is longer than average but earns its length through labeled sections for cost, billing, and behavior, with the key trigger front-loaded in the first paragraph. There is minor redundancy around 'one call and one payment' being restated, but no filler.

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?

Given the tool's complexity—billing, failure modes, batch limits—the description covers all decision-relevant facts: when to use, cost, duplicate handling, partial failure, ordering, and the sibling alternative. The output schema exists, so return structure needs less prose, and the description still summarizes it.

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. The description reinforces the urls schema (up to 5, duplicates removed) and adds the return-ordering guarantee ('in the order given') that is not in the schema. It does not add much for payment or allow_redirect, but the schema already specifies those; this is adequate and slightly above baseline.

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 opens with a specific verb and resource: pricing a product across multiple stores in one batched call. It explicitly contrasts with get_product_details and disclaims ranking/winner selection, so an agent can identify this tool as the batch variant without opening the 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?

It gives an explicit trigger ('USE THIS WHENEVER YOU HAVE MORE THAN ONE URL') and lists concrete batch use cases. It also names the cheaper single-URL alternative and the condition that should route to get_product_details, providing clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tollkit Extract 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.