Skip to main content
Glama

APEX x402 & AI Agent Tools (360 tools)

Page watch

page_watch

What changed on a web page since you last looked: pass url; the first call returns a snapshot token, call again with since= to get the text lines that appeared and disappeared. $0.005 per call over x402.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "page_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesthe public web page to watch
sinceNothe token from your previous call on this page (16 hex characters); leave out on the first call
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a solid job: it discloses the per-call price ($0.005 via x402), the snapshot-token handshake, and the shape of the result as text lines that appeared and disappeared. It does not cover failure modes, token lifetime, or payment error behavior, which keeps it below a 5.

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

Conciseness5/5

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

The definition is a single, front-loaded sentence: it leads with the purpose, then the call sequence, then the price. Every clause earns its place by adding purpose, mechanics, or cost information.

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

Completeness4/5

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

For a paid web-diff tool with no annotations and no output schema, the description covers the essential workflow, output nature, and pricing. It is still slightly incomplete on payment requirements per call and error or edge-case behavior, but it gives an agent enough to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents url, since, and payment in detail. The description reinforces the since workflow with 'since=<token>' but adds no syntax or meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb and resource: detecting what changed on a web page since the last look. It clearly implies a diff-oriented tool rather than a raw fetch, but it does not explicitly distinguish itself from sibling page tools such as page_extract or page_snap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the two-call workflow (first pass url, then pass the returned snapshot token as since) which implies repeated monitoring use. However, it gives no explicit when-to-use guidance versus alternatives and no exclusions or conditions for choosing this over the sibling page tools.

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.