Skip to main content
Glama

chgwatch__diffmulti

Batch durable-baseline diff for many URLs in one paid call. Use only=changed to get just the pages that moved. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: POST https://api.firstmention.uk/s/chgwatch/diffmulti

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": {
      "urls": "<urls>"
    },
    "name": "chgwatch__diffmulti"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNoSet to 'changed' to return only pages that differ
urlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / mode
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / only
      Added value: +{
      +  "description": "Set to 'changed' to return only pages that differ",
      +  "type": "string"
      +}
    • addedInput schema / properties / urls / items
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / urls / type
      Previous value: -"string"New value: +"array"
    • addedInput schema / required
      Added value: +[
      +  "urls"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "urls"
      -]
  3. Changed5 schema fields changed
    • removedInput schema / properties / mode
      Removed value: -{
      -  "description": "What to compare",
      -  "enum": [
      -    "text",
      -    "markdown",
      -    "meta",
      -    "links"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / store
      Removed value: -{
      -  "description": "true to save this snapshot as the new baseline",
      -  "type": "string"
      -}
    • removedInput schema / properties / url
      Removed value: -{
      -  "description": "URL to diff against its stored baseline",
      -  "type": "string"
      -}
    • addedInput schema / properties / urls
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "url"
      -]New value: +[
      +  "urls"
      +]
  4. Changed7 schema fields changed
    • removedInput schema / description
      Removed value: -"Use watchlist=1 to poll your saved list, or urls=a,b,c for a batch check. Your watchlist is stored server-side under your payer wallet, so you never resend URLs."
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "What to compare",
      +  "enum": [
      +    "text",
      +    "markdown",
      +    "meta",
      +    "links"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / store
      Added value: +{
      +  "description": "true to save this snapshot as the new baseline",
      +  "type": "string"
      +}
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "URL to diff against its stored baseline",
      +  "type": "string"
      +}
    • removedInput schema / properties / urls
      Removed value: -{
      -  "description": "Comma-separated URLs to batch-check (up to 20). Omit when watchlist=1.",
      -  "type": "string"
      -}
    • removedInput schema / properties / watchlist
      Removed value: -{
      -  "description": "Set to 1 to check every URL in your saved watchlist (keyed to your paying wallet).",
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  5. Changed3 schema fields changed
    • addedInput schema / description
      Added value: +"Use watchlist=1 to poll your saved list, or urls=a,b,c for a batch check. Your watchlist is stored server-side under your payer wallet, so you never resend URLs."
    • addedInput schema / properties / urls
      Added value: +{
      +  "description": "Comma-separated URLs to batch-check (up to 20). Omit when watchlist=1.",
      +  "type": "string"
      +}
    • addedInput schema / properties / watchlist / description
      Added value: +"Set to 1 to check every URL in your saved watchlist (keyed to your paying wallet)."
  6. Changed8 schema fields changed
    • removedInput schema / properties / baseline
      Removed value: -{
      -  "enum": [
      -    "stored",
      -    "watch"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / context_lines
      Removed value: -{
      -  "maximum": 500,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • removedInput schema / properties / mode
      Removed value: -{
      -  "enum": [
      -    "text",
      -    "markdown",
      -    "meta",
      -    "links"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / prev_hash
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / url
      Removed value: -{
      -  "description": "Single URL alternative to urls",
      -  "type": "string"
      -}
    • removedInput schema / properties / urls
      Removed value: -{
      -  "description": "Comma-separated URLs to check (max 20)",
      -  "type": "string"
      -}
    • addedInput schema / properties / watchlist
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "urls"
      -]
  7. First observed

TDQS

A3.6/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 burden and does a lot: it discloses that the call is paid, the exact price ($0.01 USDC), the chain (eip155:8453), and the payment channel (x402 in params._meta["x402/payment"]), plus the HTTP transport. It does not explain what a 'durable baseline' is, what happens on payment failure, or whether the baseline is stored server-side between calls.

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?

Front-loaded with purpose, then the filter option, then payment and endpoint details. Every sentence carries information, though the payment sentence is dense enough to require careful parsing.

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?

The paid-call mechanics and endpoint are fully covered, which is the hardest part of invoking this tool. However, with no output schema, the description never characterizes the return value — what a diff entry looks like, what the 'durable baseline' compares against, or how per-URL results are keyed — leaving a real gap for a batch tool.

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 coverage is 50%: `only` is documented in the schema already, and the description mostly repeats it, while `urls` has no schema description but is only loosely characterized as 'many URLs'. The description compensates modestly for the undocumented array parameter but adds no format or limit details (max URLs, per-URL failures).

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 ('Batch durable-baseline diff for many URLs') and distinguishes itself by scope ('many URLs in one paid call'), which sets it apart from a single-URL diff. It stops short of naming a sibling explicitly, so an agent must infer the batch-vs-single distinction from the word 'batch'.

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?

'Use only=changed to get just the pages that moved' is the only guidance, and it is really parameter-level advice rather than a when-to-use rule. There is no statement of when to prefer this over a single-URL diff, a since-based check, or a sitemap diff, so the agent must reason about the alternatives itself.

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