Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

pageaudit__vet

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/vet

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

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / seller
      Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "seller"
-]
  2. Changed3 schema fields changed
    • addedInput schema / properties / seller
      Added value: +{
+  "format": "uri",
+  "type": "string"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "seller"
+]
  3. Changed2 schema fields changed
    • removedInput schema / properties / seller
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
  4. Changed2 schema fields changed
    • addedInput schema / properties / seller
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "type": "string"
-}
  5. Changed2 schema fields changed
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / urls
      Removed value: -{
-  "type": "string"
-}
  6. Added

TDQS

C2.2/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 burden, and it does disclose genuinely useful operational facts: cost of $0.01 USDC on Base (eip155:8453), the payment envelope location params._meta["x402/payment"], and the HTTP transport. It says nothing about whether the call is read-only, what happens on an unreachable URL, or what a result contains, so the mutation/safety profile remains undisclosed.

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 first sentence is a marketing capability list that spends most of its words on features belonging to other tools, pushing the tool-specific and payment information to the tail. Payment logistics are front-loaded only after the irrelevant catalog.

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?

There is no output schema and no annotation, so the description should explain what vetting returns (verdict, status, diagnostics) and it does not. Pricing and payment mechanics are covered, but the core behavior and result shape of a paid call are left unspecified.

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 single `url` parameter has 0% schema description coverage, so the description must compensate and does not — it never explains what URL is expected, what format, or why the parameter is not marked required. Only the incidental phrase 'URL liveness preflight' weakly signals that the parameter is a target URL.

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 opens with a catalog of the whole service (page audit, SEO metadata, liveness preflight, batch vetting, change monitoring, seller search, demand data) rather than stating what the `vet` tool itself does. The agent must guess which of those seven capabilities this single-URL endpoint performs; only the phrase 'x402 endpoint vetting' in a list gives a hint, and it is mixed with capabilities that belong to siblings like audit, preflight, batch and watch.

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 statement of when to use this tool versus pageaudit__audit, pageaudit__preflight, pageaudit__batch or pageaudit__x402batch, even though the description names those very capabilities. The listing of sibling capabilities without routing guidance actively invites the agent to pick the wrong tool.

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