Anyway Possible Paid Agent Utilities

Batch URL Check ($0.01 USDC)

batch_check_urls

Read-only

Check up to ten public URLs in one paid call with isolated results for partial failures.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	Yes	One to ten public HTTP or HTTPS URLs to check independently.
`expectedStatus`	No	Optional HTTP status code expected from every URL.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`results`	Yes
`verified`	Yes
`checkedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 9, 2026

addedInput schema / properties / expectedStatus / description

Added value: +"Optional HTTP status code expected from every URL."

addedInput schema / properties / urls / description

Added value: +"One to ten public HTTP or HTTPS URLs to check independently."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "checkedAt": {
+      "type": "string"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "verified": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "verified",
+    "count",
+    "checkedAt",
+    "results"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the call is paid ($0.01 USDC), it handles partial failures with isolated results, and it is limited to public URLs. This goes beyond the schema and annotations, though it doesn't detail the exact response format for failures.

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, front-loaded sentence that conveys the core function, the limit, the paid nature, and the failure-handling behavior. No wasted words; every element earns its place.

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?

Given the output schema exists and annotations cover safety, the description is largely complete. It could explicitly mention the sibling 'check_url' for single-URL use cases, but the batch context and paid-call warning are sufficient for an agent to invoke it correctly. The 'public URLs' constraint is a useful prerequisite.

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 the schema already documents both parameters well. The description adds the 'public' constraint and 'isolated results' context, but doesn't add significant meaning beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool checks up to ten public URLs in one paid call, with a specific verb ('check'), resource ('URLs'), and scope ('up to ten', 'public'). It also distinguishes itself from a single-URL check by emphasizing the batch nature and isolated results for partial failures.

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

Usage Guidelines4/5

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

The description implies when to use this tool: when you need to check multiple URLs in one call, and it notes the paid nature. It doesn't explicitly name the sibling 'check_url' as the alternative for single-URL checks, but the batch context and 'isolated results' provide clear usage context. No explicit exclusions, but the guidance is adequate.

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.