Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

pageaudit__paycheck

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

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

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / seller
      Removed value: -{
-  "description": "The seller's paid endpoint URL to check",
-  "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: +{
+  "description": "The seller's paid endpoint URL to check",
+  "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. Added

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, and it does disclose meaningful operational facts: cost ($0.01 USDC), chain (eip155:8453 Base), the x402 payment location (params._meta["x402/payment"]), and the HTTP method/endpoint. However it says nothing about whether the call is read-only, what it returns, or what happens if payment is absent or malformed.

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 opening sentence is a long catalog of the whole product's capabilities that is not front-loaded around this tool's function. The genuinely useful part — price, chain, payment field, endpoint — is buried after marketing copy.

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 paid x402 HTTP endpoint with an undocumented optional parameter and no output schema, the description should at minimum state the tool's single function and the role of 'url'. It covers payment mechanics but leaves the core question of what the call does unanswered.

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 schema has a single optional 'url' property with zero description coverage, and the description never mentions it or explains what URL is expected or whether it is required. With only one parameter and no schema documentation, the description was the only place this could be clarified and it was 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 platform-level feature list (page audit, SEO metadata, preflight, batch vetting, monitoring, seller search, demand data) rather than a statement of what 'paycheck' itself does. An agent cannot tell from this text whether paycheck returns paid-usage data, validates an x402 payment, or performs an audit, nor how it differs from siblings like demand, sellersearch, or audit.

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 when-to-use guidance, no exclusions, and no routing to alternatives such as demand or sellersearch despite a large sibling set. The only usable context is the pricing/payment note, which tells the agent the cost of calling but not when calling is appropriate.

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