Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

pageaudit__bundle

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

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

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / seller
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / seller
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "type": "string"
-}
  3. Added

TDQS

C2.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses cost ($0.01 per call in USDC on Base via x402 in params._meta) and the HTTP endpoint, but omits whether the call is read-only, what happens if url is missing, error/402 handling, and return characteristics. Payment information is the main behavioral addition.

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

Conciseness4/5

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

A single dense paragraph front-loads the feature list and appends price and endpoint. It is reasonably compact, though the long unpunctuated list makes scanning harder and some phrases could be tightened. There is no major waste.

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

Completeness3/5

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

For a multi-feature paid bundle with no output schema and no annotations, the description gives only a high-level feature list plus payment details. It lacks return shape, whether all listed features are included in every response, and how the optional url scopes results, which are material for correct invocation.

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?

There is one optional 'url' parameter with 0% schema description coverage. The description implies a page URL via 'audit a page' and 'URL liveness preflight', but never states whether it is required, what happens if omitted, or how it is applied across the bundled features. It does not compensate for the schema gap.

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

Purpose3/5

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

The description enumerates capabilities ('audit a page, SEO metadata, URL liveness preflight, change monitoring, x402 seller search, and ... demand data'), but as a bundle it never states what one call actually returns or how it differs from siblings like pageaudit__audit or pageaudit__preflight. 'Web page intelligence for agents' is a broad category, not a specific verb+resource.

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?

No when-to-use guidance is given: it does not say to choose this over individual pageaudit tools, nor when a bundle is preferable, nor any prerequisites. An agent must infer usage from the name alone.

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