Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

pageaudit__shortlist

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

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

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / urls
      Removed value: -{
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • removedInput schema / properties / seller
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / urls
      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
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / urls
      Removed value: -{
-  "type": "string"
-}
  5. Added
  6. Removed
  7. 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 important operational details: cost of $0.01 USDC on Base (eip155:8453), payment via `params._meta["x402/payment"]`, and HTTP GET. However, it does not describe what `shortlist` returns, what side effects it has, or how its behavior differs from sibling tools.

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 description is a run-on catalog of unrelated capabilities followed by pricing and an HTTP endpoint. It is not front-loaded with the tool's specific action, and most of the capability enumeration does not help an agent invoke `shortlist` correctly.

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 definition should at least explain what `shortlist` means, what `url` controls, and what kind of result comes back. It supplies payment and endpoint metadata but leaves the core function, parameter semantics, and return behavior unexplained.

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 sole schema parameter `url` has 0% description coverage, so the description should compensate, but it never mentions or explains `url`. It only describes the separate x402 payment mechanism, leaving the declared input parameter's meaning and expected format undocumented.

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 never states what `shortlist` specifically does. Instead it lists many service capabilities (page audit, SEO metadata, URL liveness preflight, batch vetting, monitoring, seller search, demand data), none of which is tied to the name `shortlist` or distinguished from the numerous matching sibling tools.

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 for `shortlist` versus alternatives such as `pageaudit__audit`, `pageaudit__preflight`, `pageaudit__watch`, or `pageaudit__sellersearch`. The description enumerates features but does not tell an agent which request should route to this 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