Agent Utilities Hosted

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

web_page_pack

Read-only

Pack supplied HTML into bounded readable blocks with source, truncation and size estimates. No model, fetching or guaranteed token savings. FREE during validation. No key, credits or wallet. Existing source and input limits apply.

Input Schema

TableJSON Schema

Name	Required	Description
`input`	Yes
`requestId`	No	Optional legacy field; ignored in free mode.
`maxPriceMicroUsd`	No	Optional legacy field; ignored in free mode.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	Yes
`title`	Yes
`content`	Yes
`selection`	Yes
`sourceUrl`	Yes
`truncated`	Yes
`measurement`	Yes
`contentChars`	Yes
`omittedChars`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly=true, destructive=false, openWorld=false). The description adds genuine non-annotation context: no model inference, no fetching, no guaranteed token savings, free during validation, and no key/credits/wallet required. This is meaningful behavioral 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.

Conciseness4/5

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

Six short, front-loaded sentences with the core action first and the caveats/pricing after. Slightly fragmented ('No key, credits or wallet.') but nothing is padded.

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 explained, and annotations carry the safety profile. The description supplies the operationally important caveats (no fetching, no model, no guaranteed savings, free) an agent needs to select this over web_page_pack_fetch.

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 67% and the description never discusses html, maxChars, or sourceUrl directly. Terms like 'bounded', 'size estimates', and 'source' loosely map to maxChars and sourceUrl, but no syntax, defaults, or constraints are added beyond what the schema already states.

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 states a specific verb and resource: 'Pack supplied HTML into bounded readable blocks with source, truncation and size estimates.' The word 'supplied' and the phrase 'No ... fetching' implicitly separate it from the fetching sibling (web_page_pack_fetch), but the sibling is not named explicitly, so it falls short of a full 5.

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?

'No model, fetching or guaranteed token savings' plus 'Existing source and input limits apply' implies this tool is for HTML you already hold, and the presence of web_page_pack_fetch as a sibling makes the split inferable. However, no explicit when-to-use or when-to-prefer-the-alternative statement is given.

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?