Skip to main content
Glama

Agent Utilities Hosted

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

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 or wallet. Existing source and input limits apply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes
requestIdNoOptional legacy field; ignored in free mode.
maxPriceMicroUsdNoOptional legacy field; ignored in free mode.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeYes
reasonYes
statusYes
selectedYes
warningsYes
pageTypesYes
candidatesYes
selectedIdYes
canonicalUrlYes
distinctProductsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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"
+]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds genuine behavioral context beyond that: the abstain-on-ambiguity policy, the free/no-key/no-credits billing state, and that existing source and input limits still apply.

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?

Three short sentences, purpose front-loaded, with cost and limit notes trailing. No filler, though the billing sentence is somewhat repetitive ('FREE', 'No key, credits or wallet').

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, and annotations carry the safety profile. The description covers purpose, cost state, and ambiguity handling; only the parameter-level detail is thin, which is minor given a 3-param schema with 67% coverage.

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 coverage is 67%, and the description adds nothing about the html/pageUrl inputs or the two legacy fields. It gestures at 'supplied JSON-LD HTML' and the evidence sources, but adds no format, size, or semantics detail beyond what the schema already documents.

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 ('Identify the main Product or ProductGroup from supplied JSON-LD HTML') and names the evidence it uses (identity, mainEntity, canonical). It does not, however, distinguish itself from the near-identical sibling agent_utilities_main_product_preview, so an agent cannot tell the two apart from the text alone.

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?

Provides useful context ('abstain on ambiguity', 'FREE during validation') but never states when to choose this tool over the sibling preview variant or other commerce_* extractors. Usage is implied rather than directed.

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 toolsInspect
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