Skip to main content
Glama

BRAINIAC Web & Page Intelligence

Detect page changes

web-intelligence_page-change-detect
Read-onlyIdempotent

Fetch a public page and compare its Markdown with a caller-supplied previous snapshot. The snapshot is not stored. The result lists added and removed lines and does not rank their importance. Price $0.05 USDC. POST /api/v1/web-intelligence/page-change-detect. An unpaid call returns the x402 payment terms and does not run.

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>",
      "previousMarkdown": "<previousMarkdown>"
    },
    "name": "web-intelligence_page-change-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesurl, string, length 8 to 2000. Required.
previousMarkdownYespreviousMarkdown, string, length 0 to 200000. Required.
previousRetrievedAtNopreviousRetrievedAt, string, date-time. Optional.

Output Schema

NameRequiredDescriptionDefault
changedNochanged. Boolean.
changesNochanges. Array.
sourcesNosources. Array.
finalUrlNofinalUrl. String.
warningsNowarnings. Array.
httpStatusNohttpStatus. Number.
contentTypeNocontentType. String.
currentHashNocurrentHash. String.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
previousHashNopreviousHash. String.
requestedUrlNorequestedUrl. String.
currentMarkdownNocurrentMarkdown. String.
previousRetrievedAtNopreviousRetrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the bar is lower. The description still adds real context the agent could not otherwise know: the snapshot is not persisted, diff results are unranked, the call costs $0.05 USDC, and an unpaid call returns x402 payment terms without running.

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?

Four compact sentences, front-loaded with behavior, then pricing, transport, and the payment failure mode. No redundant restatement of the name or title.

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

Completeness5/5

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

With an output schema, return detail is not required, and the description still summarizes the diff shape (added and removed lines, unranked). Combined with payment and non-persistence notes, nothing an agent needs to invoke it correctly is missing.

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 100%, so the baseline is 3. The description clarifies that previousMarkdown is a prior snapshot and that it must be supplied by the caller, but it says nothing about previousRetrievedAt or the size/format constraints, which the schema already carries.

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

Purpose5/5

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

States a specific verb and resource: fetch a public page and diff its Markdown against a caller-supplied snapshot. This clearly separates it from the sibling fetch tools (url-to-markdown, structured-page-extract), which retrieve but do not compare.

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?

The description implies usage ('caller-supplied previous snapshot', 'snapshot is not stored') but never states when to pick this over a sibling such as url-to-markdown, nor any exclusions. Payment behavior is mentioned, but it is a protocol note rather than selection guidance.

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