Skip to main content
Glama

pageaudit__audit

Web page intelligence for agents: audit pages, check SEO metadata, preflight URL liveness, monitor pages for changes, vet x402 sellers, and compare perp funding rates across Binance/OKX/Bybit/Gate. $0.01/call USDC on Base; free real previews. 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/audit

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

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  2. Changed2 schema fields changed
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  3. Changed1 schema field changed
    • removedInput schema / properties / check_links
      Removed value: -{
      -  "type": "number"
      -}
  4. Changed3 schema fields changed
    • addedInput schema / properties / check_links
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / url
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / urls
      Removed value: -{
      -  "type": "string"
      -}
  5. Changed3 schema fields changed
    • removedInput schema / properties / check_links
      Removed value: -{
      -  "type": "number"
      -}
    • removedInput schema / properties / url
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / urls
      Added value: +{
      +  "type": "string"
      +}
  6. Changed4 schema fields changed
    • removedInput schema / properties / check_links / maximum
      Removed value: -15
    • removedInput schema / properties / check_links / minimum
      Removed value: -0
    • changedInput schema / properties / check_links / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  7. Changed2 schema fields changed
    • addedInput schema / properties / check_links
      Added value: +{
      +  "maximum": 15,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • removedInput schema / properties / url / description
      Removed value: -"Page URL to audit (https)"
  8. Changed3 schema fields changed
    • removedInput schema / properties / link_cap
      Removed value: -{
      -  "description": "How many links to health-check (default 10, max 50).",
      -  "type": "number"
      -}
    • removedInput schema / properties / timeout_ms
      Removed value: -{
      -  "description": "Per-request timeout in ms.",
      -  "type": "number"
      -}
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) page to audit."New value: +"Page URL to audit (https)"
  9. Changed6 schema fields changed
    • removedInput schema / properties / check_links
      Removed value: -{
      -  "description": "Number of unique links to health-check (0-15, default 0)",
      -  "maximum": 15,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • addedInput schema / properties / link_cap
      Added value: +{
      +  "description": "How many links to health-check (default 10, max 50).",
      +  "type": "number"
      +}
    • removedInput schema / properties / max_markdown_chars
      Removed value: -{
      -  "description": "Cap on returned markdown length (1000-200000, default 40000)",
      -  "maximum": 200000,
      -  "minimum": 1000,
      -  "type": "integer"
      -}
    • addedInput schema / properties / timeout_ms
      Added value: +{
      +  "description": "Per-request timeout in ms.",
      +  "type": "number"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) page to audit"New value: +"Public http(s) page to audit."
    • removedInput schema / properties / url / format
      Removed value: -"uri"
  10. First observed

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 genuine behavioral facts the schema does not: the $0.01 USDC-on-Base price, the x402 payment rail via params._meta["x402/payment"], free previews, and the HTTP endpoint. However it never says what an audit returns, how failures or unreachable URLs are reported, or that the payment field is not declared in the input schema — a real gap for a metered call.

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?

Pricing is stated twice ("$0.01/call USDC on Base; free real previews" then "Price: $0.01 per call in USDC on Base (eip155:8453)"), wasting the limited budget. The capability catalogue also crowds out the one thing the tool actually needs: a statement of what audit does with the url.

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 single-parameter, no-annotation, no-output-schema tool, the description should at minimum define the parameter and the audit's output shape. Instead it spends its length on platform-wide marketing and duplicated payment terms, leaving the agent unable to predict the response or confirm the required input.

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?

Schema coverage is 0% on the single `url` parameter, and required count is 0, yet the description never states whether `url` is the page to audit, whether it is required, or what forms it accepts. The word "pages" weakly implies it, but the agent gets no confirmation from either the schema or the prose.

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 name-plus-title assertion collapses to "audit pages," which largely restates the tool name pageaudit__audit. The rest of the sentence enumerates capabilities that belong to siblings (preflight liveness, change monitoring, seller vetting, perp funding rates), so the agent cannot tell what this specific tool does that pageaudit__preflight or pageaudit__funding does not.

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?

The only routing hint is "free real previews," which implies trying a preview before paying, but no sibling is named as the alternative and no condition selects audit over preflight/watch/vet. With 20 siblings in the catalog, the absence of any disambiguation leaves selection to guesswork.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources