Agent Utilities Hosted

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

web_wikipedia_read

Read-only

Read a public Wikipedia article through the official API with revision, license, sections and a text budget. Ten supported editions; inspect omissions. 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
`retrievedAt`	Yes
`omittedChars`	Yes
`linksTruncated`	Yes
`retrievalScope`	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 cover read-only/open-world safety, and the description still adds real behavior: official API source, free during validation, no key/credits/wallet required, a text budget, and that source/input limits apply. 'Inspect omissions' usefully warns the agent that truncated content must be checked. It leaves the odd idempotentHint=false unaddressed.

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

Conciseness3/5

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

Front-loads the core purpose, but the back half is a choppy stack of fragments ('FREE during validation. No key, credits or wallet.') that partially restate the same cost point and read more like marketing copy than operational guidance.

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-value explanation is not required, and the description covers editions, license, revision, and budget. However, for a tool with nested input and a required url, it omits the supported-edition list and url/section format expectations, leaving some call-time ambiguity.

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?

With 67% schema coverage, the description compensates by mapping concepts to parameters: 'sections' to section, 'text budget' to maxChars, and 'Existing source and input limits apply' to the legacy requestId/maxPriceMicroUsd fields. It does not give syntax details (URL format, section naming), but it meaningfully extends the schema.

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 ('Read a public Wikipedia article through the official API') and names the payload it returns (revision, license, sections, text budget). It is clearly distinct from pack/popular siblings, though it never explicitly contrasts itself with web_wikipedia_pack or web_wikipedia_popular.

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?

Hints at context: 'Ten supported editions' and 'inspect omissions' tell the agent the output may be truncated and limited in coverage, and 'FREE during validation' signals cost. But it never says when to pick this over web_wikipedia_pack or web_readable_fetch, so the routing guidance 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?