Skip to main content
Glama

Agent Utilities Hosted

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

commerce_unit_price

Read-only

Compare up to 50 explicit pack prices with exact arithmetic across compatible mass, volume or count units; no currency conversion. 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
offersYes
currencyYes
referenceYes
cheapestIdsYes

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. First observed

TDQS

A4.2/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. The description adds valuable behavioral context beyond annotations: it is free, requires no key or wallet, operates on up to 50 offers, performs exact arithmetic, and does not convert currencies. It does not disclose output details, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences that front-load the comparison scope and then list operational constraints. Every clause contributes: limits, arithmetic behavior, pricing mode, and prerequisites.

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 an output schema exists, the description need not explain return values. It covers the key behavioral constraints an agent needs: read-only, free access, no currency conversion, exact arithmetic, 50-item limit, and that legacy parameters are ignored. This is sufficient for correct invocation.

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 description coverage is 67%, with two legacy parameters clearly described as ignored in free mode. The description adds meaning by clarifying the 50-offer limit and the exact-arithmetic/no-currency-conversion constraint, which helps interpret the required input fields. It does not explain the reference unit semantics in detail, but the schema provides enums and patterns.

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: comparing up to 50 pack prices with exact arithmetic across compatible mass, volume or count units, and explicitly excludes currency conversion. This distinguishes it from siblings like commerce_pack_size_normalize or commerce_price_components, though the core action of normalizing to a reference unit is left implicit.

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

Usage Guidelines4/5

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

The description gives clear context: comparing explicit pack prices with no currency conversion and within compatible units. It does not explicitly name sibling tools or state when to prefer alternatives like commerce_pack_plan, but the constraints and scope provide strong usage boundaries.

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