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 commerce_pack_plan after separate spending approval.

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

A4.4/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses that the tool performs no network fetch, requires no payment/key, and has no paid fallback, plus a 4096-byte input cap. It also clarifies the financial scope by stating exact item subtotal only and excluding shipping/tax/fees.

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?

Four compact sentences, all information-bearing, with the main purpose and key constraints front-loaded. No filler or repeated schema content.

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?

The description covers scale limits, cost semantics, side-effect behavior, and the paid alternative, and the output schema covers return structure. It does not explain how to interpret the offers/requiredUnits relationship in detail, but the example schema largely fills that gap.

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?

With 0% schema description coverage, the description partially compensates by encoding limits for offers, required units, units per pack, and packs per offer, and by clarifying price meaning (exact item subtotal). However, currency and minorUnitDigits semantics still depend on the example and schema patterns, so the compensation is incomplete.

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 identifies the resource as 'custom pack planning' and adds concrete scope constraints (up to 3 offers, unit/pack limits, exact item subtotal). It distinguishes itself from the paid commerce_pack_plan, though the precise operation—selecting offers to satisfy requiredUnits—is more implied than stated.

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

Usage Guidelines5/5

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

It explicitly positions the tool as the FREE planning path and directs larger tasks to commerce_pack_plan after separate spending approval. The limits and exclusions (no key, payment, network fetch, paid fallback) tell an agent exactly when this tool applies.

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?