Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

pageaudit__txpreflight

Web page intelligence for agents: audit a page, SEO metadata, URL liveness preflight, change monitoring, x402 seller search, and real 30-day paid-usage demand data for the x402 market (34k endpoints). 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/txpreflight

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

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / tx
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • removedInput schema / properties / seller
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / tx
      Added value: +{
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / seller
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "type": "string"
-}
  4. Changed2 schema fields changed
    • removedInput schema / properties / tx
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
  5. Added
  6. Removed
  7. Changed3 schema fields changed
    • removedInput schema / properties / seller
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / tx
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / urls
      Added value: +{
+  "type": "string"
+}
  8. Added

TDQS

C2.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two genuinely useful facts the schema cannot convey: the cost ($0.01 per call in USDC on Base, eip155:8453) and the payment mechanism (`params._meta["x402/payment"]`), plus the HTTP verb and endpoint. However, it never states whether the call is read-only, what it returns, or what happens if payment is omitted, so important behavioral traits remain hidden.

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?

The lead is a vague marketing phrase ("Web page intelligence for agents") rather than a statement of function, and the sentence then degenerates into a six-item capability list plus pricing and transport details. Nothing is front-loaded around this tool's actual job, and most of the enumeration does not earn its place for a single-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no annotations and no output schema, the description should at minimum say what the preflight checks and what the caller gets back. It supplies price and payment mechanics but leaves the actual result and semantics unexplained, so an agent cannot predict the outcome of a call.

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?

There is one parameter (`url`) at 0% schema description coverage, so the description must compensate. "Audit a page" implies the url is the target page, but the description adds no format, validation, or scope detail (e.g., whether schemes or paths are accepted) beyond that inference.

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 enumerates six unrelated capabilities ("audit a page, SEO metadata, URL liveness preflight, change monitoring, x402 seller search, and... demand data") that read as a product-line blurb rather than a statement of what this specific tool `txpreflight` does. The name and endpoint (`/pageaudit/txpreflight`) suggest a preflight check, but the text never commits to that, so an agent cannot distinguish it from `pageaudit__preflight`, `pageaudit__audit`, or `chainread__txpreflight`.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many similarly named siblings (`pageaudit__preflight`, `txpreflight__preflight`, `x402_preflight__check`). "URL liveness preflight" is the only hint, and it is buried mid-list with no conditions or exclusions attached.

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

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