Agent Utilities Hosted

by dev.workers.agent-utilities.agent-utilities

commerce_feed_page_compare

Read-only

Compare supplied feed identity, price, currency and availability with selected JSON-LD product evidence; preserve conflicts and unknown fields. Optional availabilityProfile google_merchant applies Google feed mappings; generic is the default. FREE during validation. No key, credits, wallet or preparation needed. Supply your task in input. Existing source and input limits apply.

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`scope`	Yes
`checks`	Yes
`status`	Yes
`evidence`	Yes
`warnings`	Yes
`selection`	Yes
`identityStatus`	Yes
`availabilityProfile`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 13, 2026

removedInput schema / properties / maxPriceMicroUsd

Removed value: -{
-  "description": "Optional legacy field; ignored in free mode.",
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / requestId

Removed value: -{
-  "description": "Optional legacy field; ignored in free mode.",
-  "type": "string"
-}

Changed5 schema fields changedOct 6, 2026

changedInput schema / properties / maxPriceMicroUsd / description

Previous value: -"Explicit maximum new debit; 0 means recovery only."New value: +"Optional legacy field; ignored in free mode."

removedInput schema / properties / maxPriceMicroUsd / maximum
```
Removed value: -999999999999
```

changedInput schema / properties / requestId / description

Previous value: -"Persist the ID returned by agent_utilities_prepare. Reuse after uncertainty."New value: +"Optional legacy field; ignored in free mode."

removedInput schema / properties / requestId / pattern
```
Removed value: -"^\\d{13}_[A-Za-z0-9_-]{16,80}$"
```

changedInput schema / required

Previous value: -[
-  "input",
-  "requestId",
-  "maxPriceMicroUsd"
-]New value: +[
+  "input"
+]

Changed4 schema fields changedSep 29, 2026

addedInput schema / properties / input / properties / availabilityProfile

Added value: +{
+  "description": "Default generic preserves existing vocabulary distinctions. google_merchant maps non-vehicle Schema.org availability to Google feed categories; not an eligibility check.",
+  "enum": [
+    "generic",
+    "google_merchant"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / availabilityProfile

Added value: +{
+  "enum": [
+    "generic",
+    "google_merchant"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / evidence / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "offerSources": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "offerBlock": {
-              "type": "number"
-            },
-            "offerPointer": {
-              "type": "string"
-            },
-            "productBlock": {
-              "type": "number"
-            },
-            "productPointer": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "productBlock",
-            "productPointer",
-            "offerBlock",
-            "offerPointer"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "productSources": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "block": {
-              "type": "number"
-            },
-            "pointer": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "block",
-            "pointer"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "productSources",
-      "offerSources"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "offerSources": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "offerBlock": {
+              "type": "number"
+            },
+            "offerPointer": {
+              "type": "string"
+            },
+            "productBlock": {
+              "type": "number"
+            },
+            "productPointer": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "productBlock",
+            "productPointer",
+            "offerBlock",
+            "offerPointer"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "originalAvailability": {
+        "items": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": "array"
+      },
+      "productSources": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "block": {
+              "type": "number"
+            },
+            "pointer": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "block",
+            "pointer"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "productSources",
+      "offerSources",
+      "originalAvailability"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / required

Previous value: -[
-  "status",
-  "identityStatus",
-  "selection",
-  "checks",
-  "evidence",
-  "warnings",
-  "scope"
-]New value: +[
+  "status",
+  "identityStatus",
+  "availabilityProfile",
+  "selection",
+  "checks",
+  "evidence",
+  "warnings",
+  "scope"
+]

AddedSep 21, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lowered. The description adds genuinely useful non-schema context: conflicts and unknown fields are preserved, the operation is FREE during validation, and it needs no key/credits/wallet. It does not explain limits despite referencing 'existing source and input limits apply'.

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?

The core comparison is front-loaded and earns its place, but trailing sentences ('FREE during validation. No key, credits, wallet or preparation needed. Supply your task in input. Existing source and input limits apply.') are boilerplate and 'Supply your task in input' is vague for an object-typed input. Roughly half the text is 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?

An output schema exists, so return values need no explanation, which reduces the burden. The description adequately conveys the comparison and billing model, but with a nested 1-parameter schema at 0% description coverage it leaves the html/pageUrl/offerUrl inputs unexplained, so it is adequate but not complete.

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 description coverage is 0%, so the description must carry parameter meaning. It does name the feed fields (identity, price, currency, availability) and explains the availabilityProfile enum trade-off (google_merchant vs generic default), but it says nothing about the top-level html, pageUrl, and offerUrl parameters, whose roles remain opaque from the schema alone.

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?

States a specific verb+resource triple: it compares supplied feed identity/price/currency/availability against selected JSON-LD product evidence. An agent can tell it apart from extraction siblings like commerce_offer_extract or html_jsonld, since this one is a comparison of the two. It does not, however, name its closest sibling (agent_utilities_feed_page_compare_preview) or clarify their difference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance relative to alternatives. The description only notes 'generic is the default' for the profile and states cost/billing terms, leaving the agent to infer that this tool is for feed-vs-JSON-LD reconciliation. No exclusions or prerequisite conditions are provided.

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

All Agent Utilities Hosted 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.

Resources

Need Help?