automaton

pageaudit__preflight

Verdict per URL before you pay or cite it: live/parked/lander/dead + final_url after redirects, status, redirect count, title, bytes. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/pageaudit/preflight

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pageaudit__preflight"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

addedInput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / urls

Removed value: -{
-  "description": "Comma-separated URLs (max 20)",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "urls"
-]
```

Changed3 schema fields changedNov 6, 2026

removedInput schema / properties / url

Removed value: -{
-  "type": "string"
-}

addedInput schema / properties / urls

Added value: +{
+  "description": "Comma-separated URLs (max 20)",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "urls"
+]
```

Changed2 schema fields changedNov 3, 2026
- addedInput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / urls
```
Removed value: -{
-  "type": "string"
-}
```
Changed3 schema fields changedNov 2, 2026
- removedInput schema / properties / excerpt
```
Removed value: -{
-  "maximum": 2000,
-  "minimum": 0,
-  "type": "integer"
-}
```
- removedInput schema / properties / url
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / urls / description
```
Removed value: -"comma list, up to 20"
```
AddedNov 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations exist, so the description carries the full load and does well on the operationally critical parts: exact cost ($0.01 USDC on Base, eip155:8453), the x402 payment mechanism, and the transport (HTTP GET endpoint). It does not describe failure/error behavior or rate limits, so the disclosure is strong but incomplete.

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?

One dense, front-loaded block: verdict and return fields first, then price/payment mechanics, then endpoint. Every clause carries information; nothing is filler.

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 one-parameter, no-output-schema tool with zero annotations, this covers purpose, cost, payment mechanics, transport, and the fields returned. The main remaining gap is what a failed lookup or an unpaid call looks like to the caller.

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?

The single 'url' parameter has 0% schema coverage and no description, but its meaning is unambiguous from the name. More importantly, the description documents a payment input (params._meta["x402/payment"]) that does not appear in the input schema at all — a genuinely non-obvious requirement the schema fails to capture.

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?

Names a specific verb and resource: a per-URL verdict classifying pages as live/parked/lander/dead after redirect resolution. The output fields (final_url, status, redirect count, title, bytes) make the deliverable concrete. It stops short of distinguishing itself from closely related siblings like pageaudit__audit or pageaudit__vet.

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?

'Before you pay or cite it' gives a genuine usage condition — this is a cheap pre-check gate. However, with many overlapping siblings (audit, vet, peek, addrcheck) present in the catalog, the description offers no routing guidance about when to escalate to a fuller audit instead of a preflight.

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

All automaton 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?