Agent Utilities Hosted

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

web_wikipedia_pack

Read-only

Pack supplied Wikipedia article HTML with sections, source links, attribution and a bounded text budget. No fetching or generated summary. 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
`links`	Yes
`scope`	Yes
`title`	Yes
`source`	Yes
`content`	Yes
`sections`	Yes
`selection`	Yes
`truncated`	Yes
`measurement`	Yes
`omittedChars`	Yes
`linksTruncated`	Yes
`outlineTruncated`	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 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive and non-open-world behavior, and the description is consistent with them. It adds genuinely new context beyond the structured fields: no fetching, no generated summary, free during validation, and no key/credits/wallet required. It still omits what happens when the HTML or maxChars bounds are exceeded.

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 no filler; the core packing behavior leads and pricing/limit caveats follow. The telegraphic style ('FREE during validation. No key, credits or wallet.') is efficient, if slightly fragmented.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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. For a nested-input packing tool the description is adequate but leaves gaps: it does not explain the section-selection behavior, the maxChars truncation semantics, or the sibling it replaces.

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% but the required html/sourceUrl and the section/maxChars fields carry no inline descriptions. The description gestures at them ('sections', 'source links', 'bounded text budget') but adds no format or selection semantics beyond naming the concepts.

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: it 'packs' supplied Wikipedia article HTML into sections, source links, attribution and a bounded text budget. The phrase 'No fetching' implicitly separates it from the read/fetch siblings, but no sibling is named explicitly, so an agent must infer the boundary.

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 fetching or generated summary' tells the agent this tool consumes HTML rather than retrieving it, and 'Existing source and input limits apply' hints at prerequisites. However, it never names the alternative (e.g. web_wikipedia_read) that should supply the HTML, so the when-to-use routing 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?