Agent Utilities Hosted

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

commerce_offer_extract

Read-only

Extract bounded Product offers from supplied JSON-LD HTML with source pointers, missing-price warnings and separate aggregate ranges. 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
`offers`	Yes
`truncated`	Yes
`invalidBlocks`	Yes
`productsFound`	Yes
`unsupportedOffers`	Yes
`unresolvedReferences`	Yes
`productsWithoutOffers`	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"
+]

First observedSep 19, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=false, so safety is covered. The description adds the bounded nature, missing-price warnings, separate aggregate ranges, and free/no-key auth context, which is useful. It does not state what happens to existing data (nothing, since read-only) or rate limits beyond 'existing source and input limits apply', which is vague.

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-loads the action in the first sentence and keeps the operational guarantees (free, no key, limits) short. The 'Supply your task in input' clause is filler that could be removed, but overall it is tight.

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 not be explained, and annotations cover safety. However, the 0%-coverage nested schema and the ambiguous 'source and input limits apply' leave the agent without needed detail on html format, baseUrl's role for resolving pointers, or how maxOffers interacts with 'bounded'.

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 0% for the nested input object (html, baseUrl, maxOffers), and the description does not compensate — it only says 'Supply your task in input', adding no meaning for html, baseUrl, or maxOffers. This is a real gap given maxOffers bounds the 'bounded' output.

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 and resource: 'Extract bounded Product offers from supplied JSON-LD HTML'. Distinguishes from sibling html_jsonld (generic JSON-LD) and commerce_offer-related previews, though it doesn't explicitly name the alternative it differs from. The purpose is clear 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 Guidelines3/5

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

Implies when-to-use via 'from supplied JSON-LD HTML' but never states when to prefer it over html_jsonld or commerce_main_product, and offers no exclusions. The 'Supply your task in input' phrasing is misleadingly generic rather than listing preconditions.

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?