Agent Utilities Hosted

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

commerce_main_product

Read-only

Identify the main Product or ProductGroup from supplied JSON-LD HTML using identity, mainEntity and canonical evidence; abstain on ambiguity. 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
`reason`	Yes
`status`	Yes
`selected`	Yes
`warnings`	Yes
`pageTypes`	Yes
`candidates`	Yes
`selectedId`	Yes
`canonicalUrl`	Yes
`distinctProducts`	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"
+]

AddedSep 21, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already establish the read-only, closed-world, non-destructive profile. The description adds genuine extra context: it abstains on ambiguity, notes it is free during validation with no key/credits/wallet needed, and warns that source and input limits apply. The idempotentHint=false is left unexplained, which is the only notable gap.

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?

Four short sentences, front-loaded with the purpose statement and the abstain rule, with cost/limits trailing. Most sentences earn their place, though 'Supply your task in input' is an awkward, low-information phrasing.

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

Completeness4/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 described. For a single-purpose JSON-LD extraction tool, the description covers purpose, ambiguity behavior, and cost. The main omission is any explanation of the nested input object's fields.

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%, so the description must carry the burden, but it only says 'Supply your task in input.' That is vague and does not clarify the nested html (required) vs. pageUrl fields or the 2048/100000 length constraints the schema imposes without prose.

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?

The description names a specific verb (Identify) and resource (main Product or ProductGroup) and scopes the input domain to supplied JSON-LD HTML. This distinguishes it from generic extractors like html_jsonld or commerce_offer_extract, though it does not explicitly name the sibling it differs from (e.g. agent_utilities_main_product_preview).

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?

Usage is implied by the input condition ('supplied JSON-LD HTML') and the 'abstain on ambiguity' rule gives one behavioral trigger. But there is no explicit when-to-use vs. alternative guidance, no exclusions, and nothing telling the agent why to pick this over the preview sibling or html_jsonld.

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?