Anyway Possible Paid Agent Utilities

Verify Web Evidence ($0.01 USDC)

verify_web_evidence

Read-only

Verify one public URL and return timestamped status, redirects, metadata, content hash, and a receipt.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Public HTTP or HTTPS URL whose current contents should be verified.
`expectedText`	No	Optional case-insensitive text that must appear in the bounded response body.
`expectedStatus`	No	Optional HTTP status code that the final response must match.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`title`	No
`status`	Yes
`finalUrl`	Yes
`verified`	Yes
`receiptId`	Yes
`observedAt`	Yes
`contentSha256`	Yes
`redirectChain`	Yes
`responseTimeMs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 9, 2026

addedInput schema / properties / expectedStatus / description

Added value: +"Optional HTTP status code that the final response must match."

addedInput schema / properties / expectedText / description

Added value: +"Optional case-insensitive text that must appear in the bounded response body."

addedInput schema / properties / url / description

Added value: +"Public HTTP or HTTPS URL whose current contents should be verified."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "contentSha256": {
+      "type": "string"
+    },
+    "finalUrl": {
+      "format": "uri",
+      "type": "string"
+    },
+    "observedAt": {
+      "type": "string"
+    },
+    "receiptId": {
+      "type": "string"
+    },
+    "redirectChain": {
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "responseTimeMs": {
+      "type": "integer"
+    },
+    "status": {
+      "type": "integer"
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verified": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "verified",
+    "status",
+    "finalUrl",
+    "redirectChain",
+    "responseTimeMs",
+    "contentSha256",
+    "receiptId",
+    "observedAt"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover readOnlyHint=true and destructiveHint=false, and the description adds useful detail about redirects, content hashing, and a receipt. However, it does not disclose limits, timeouts, authentication needs, or the meaning of the cost/receipt behavior beyond what the title already signals.

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?

The description is a single sentence that front-loads the core action and enumerates the returned artifacts without padding. Every phrase earns its place, and there is no redundant wording.

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?

For a low-complexity, three-parameter tool with full schema documentation, an output schema, and read-only/non-destructive annotations, the description is mostly complete. The main missing piece is sibling differentiation, but an agent can still invoke it correctly using the schema and the clear artifact list.

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 100%, so each parameter is already documented in the schema, including URL format, expectedText length, and expectedStatus range. The tool description adds no parameter-level semantics beyond saying the URL must be public and singular.

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 action and resource: verify one public URL and return a defined set of artifacts (timestamped status, redirects, metadata, content hash, receipt). It distinguishes itself from batch_check_urls through the singular 'one', but it does not explicitly differentiate itself from the similarly-named check_url, so it stops short of full sibling distinction.

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?

The wording 'one public URL' implies single-URL verification and therefore suggests it is not for batch checks, but there is no explicit when-to-use guidance and no mention of alternatives such as check_url or batch_check_urls. Usage context is only implied, not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Anyway Possible Paid Agent Utilities 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.