Agent Utilities Hosted

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

agent_utilities_pack_preview

Read-onlyIdempotent

FREE custom pack planning. Up to 3 interchangeable offers, 1000 required units, 1000 units per pack and 50 packs per offer; 4096 input bytes. Exact item subtotal only; excludes shipping, tax and fees. No key, payment, network fetch or paid fallback. Larger tasks may use the free commerce_pack_plan full tool within its limits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`offers`	Yes
`currency`	Yes
`requiredUnits`	Yes
`minorUnitDigits`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	Yes
`scope`	Yes
`limits`	Yes
`result`	Yes
`chargedMicroUsd`	Yes
`executionPerformed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 20, 2026
- changedInput schema / properties / offers / items / properties / unitsPerPack / maximum
```
Previous value: -50New value: +1000
```
- changedInput schema / properties / requiredUnits / maximum
```
Previous value: -50New value: +1000
```
- changedOutput schema / properties / limits / properties / maxRequiredUnits / const
```
Previous value: -50New value: +1000
```
- changedOutput schema / properties / limits / properties / maxUnitsPerPack / const
```
Previous value: -50New value: +1000
```

Changed2 schema fields changedSep 19, 2026

addedInput schema / examples

Added value: +[
+  {
+    "currency": "USD",
+    "minorUnitDigits": 2,
+    "offers": [
+      {
+        "id": "six-pack",
+        "maxPacks": 10,
+        "price": "7.99",
+        "unitsPerPack": 6
+      },
+      {
+        "id": "ten-pack",
+        "maxPacks": 10,
+        "price": "11.99",
+        "unitsPerPack": 10
+      }
+    ],
+    "requiredUnits": 12
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "chargedMicroUsd": {
+      "const": "0",
+      "type": "string"
+    },
+    "executionPerformed": {
+      "const": true,
+      "type": "boolean"
+    },
+    "limits": {
+      "additionalProperties": false,
+      "properties": {
+        "maxInputBytes": {
+          "const": 4096,
+          "type": "integer"
+        },
+        "maxOffers": {
+          "const": 3,
+          "type": "integer"
+        },
+        "maxPacksPerOffer": {
+          "const": 50,
+          "type": "integer"
+        },
+        "maxRequiredUnits": {
+          "const": 50,
+          "type": "integer"
+        },
+        "maxUnitsPerPack": {
+          "const": 50,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "maxOffers",
+        "maxRequiredUnits",
+        "maxUnitsPerPack",
+        "maxPacksPerOffer",
+        "maxInputBytes"
+      ],
+      "type": "object"
+    },
+    "mode": {
+      "const": "free-preview",
+      "type": "string"
+    },
+    "result": {
+      "additionalProperties": false,
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "excessUnits": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "feasible": {
+          "type": "boolean"
+        },
+        "itemSubtotal": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "lines": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "lineSubtotal": {
+                "type": "string"
+              },
+              "packs": {
+                "type": "number"
+              },
+              "units": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "id",
+              "packs",
+              "units",
+              "lineSubtotal"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "minorUnitDigits": {
+          "type": "number"
+        },
+        "packCount": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "requiredUnits": {
+          "type": "number"
+        },
+        "scope": {
+          "type": "string"
+        },
+        "totalUnits": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "currency",
+        "minorUnitDigits",
+        "requiredUnits",
+        "feasible",
+        "totalUnits",
+        "excessUnits",
+        "itemSubtotal",
+        "packCount",
+        "lines",
+        "scope"
+      ],
+      "type": "object"
+    },
+    "scope": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode",
+    "executionPerformed",
+    "chargedMicroUsd",
+    "result",
+    "limits",
+    "scope"
+  ],
+  "type": "object"
+}

AddedSep 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety bar is low. The description still adds real context: no key/payment/network fetch or paid fallback, a 4096 input-byte cap, and itemized numeric limits (3 offers, 1000 units, 1000 units/pack, 50 packs/offer). That is useful disclosure beyond the structured fields.

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?

Dense but front-loaded: purpose first, then limits, then cost scope, then auth/network caveats, then the alternative routing. Every clause carries information (limits, exclusions, no-key, alternative) with no filler.

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 no explanation, and annotations cover the safety profile. The description supplies what those fields can't: the exact envelope constraints and the 'exact item subtotal only; excludes shipping, tax, fees' costing semantics. Only the currency/minorUnitDigits meaning is left uncovered.

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 compensate. It references offers count, required units, units-per-pack and packs-per-offer caps, which map to the schema constraints, but it never explains the semantics of 'currency' or 'minorUnitDigits', nor the per-offer id/price fields. Compensation is partial.

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 ('custom pack planning') and distinguishes itself from the sibling commerce_pack_plan, which it explicitly names as the 'full tool'. An agent can tell it is a bounded preview variant rather than the general planner, though it never restates what the output actually is.

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?

It hints at routing ('Larger tasks may use the free commerce_pack_plan full tool within its limits') and lists hard limits that imply when this is and is not sufficient. However, the boundary condition is vague ('within its limits') and there is no explicit when-to-use/when-not statement, so usage is only implied.

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?