automaton

pageaudit__addrcheck

Web page intelligence for agents: page audit, SEO metadata, URL liveness preflight, batch x402 endpoint vetting, change monitoring, x402 seller search, and real 30-day paid-usage demand data for the x402 market. 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/addrcheck

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__addrcheck"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026
- removedInput schema / properties / address
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```
Changed2 schema fields changedNov 6, 2026
- addedInput schema / properties / address
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / seller
```
Removed value: -{
-  "type": "string"
-}
```
Changed2 schema fields changedNov 6, 2026
- addedInput schema / properties / seller
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / url
```
Removed value: -{
-  "type": "string"
-}
```
Changed2 schema fields changedNov 6, 2026
- removedInput schema / properties / addr
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```
AddedNov 6, 2026
RemovedNov 3, 2026
AddedNov 2, 2026

TDQS

C2.2/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose genuinely useful behavior beyond structured fields: a $0.01 USDC-on-Base price, the x402 payment payload location (params._meta["x402/payment"]), and the backing HTTP endpoint. It omits whether the call is read-only, what happens on payment failure, and what the response contains, leaving the safety and failure profile undocumented.

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

Conciseness2/5

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

Everything is packed into one run-on comma-separated list of the whole product suite, which buries any addrcheck-specific signal. The payment and endpoint sentences are legitimately valuable, but the capability list does not earn its space because none of it is scoped to this tool.

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?

The definition is poor: the tool is trivial (one optional string, no output schema, no annotations), yet an agent still cannot tell what addrcheck returns or when it beats its siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has one parameter ('url') at 0% schema description coverage, and the description never mentions it, its format, or whether it is required (required list is empty). The only tangential hint is the phrase 'URL liveness preflight', which belongs to a different sibling's capability. With zero schema coverage, the description should have compensated and does not.

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

Purpose2/5

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

The description is a suite-level tagline listing seven unrelated capabilities (page audit, SEO metadata, preflight, batch vetting, monitoring, seller search, demand data) rather than stating what THIS tool does. The name 'addrcheck' implies checking an address, but nothing in the text confirms or explains that. It actually restates the domain of its siblings (pageaudit__audit, pageaudit__preflight, pageaudit__batch) without distinguishing this tool from any of them.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no when-not-to-use, and no routing to alternatives, despite 18 sibling tools covering overlapping capabilities. An agent cannot infer from this text whether to call addrcheck versus audit, preflight, vet, or peek for a given URL task.

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?