Skip to main content
Glama

NS Pros MCP Gateway

nobel__archive_compare

What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and both capture timestamps with their gaps from the requested dates. It diffs readable text, not markup, so a restyled page with the same words reads changed:false. Identical captures answer changed:false with the reason (sa

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://www.ftc.gov/policy-notices/privacy-policy",
      "date_a": "2022-06-02",
      "date_b": "2024-06-15"
    },
    "name": "nobel__archive_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page address, e.g. "https://www.ftc.gov/policy-notices/privacy-policy".
date_aYesThe earlier date, as YYYY-MM-DD (e.g. "2021-06-01").
date_bYesThe later date, as YYYY-MM-DD (e.g. "2024-06-01").
max_gap_daysNoFurthest a capture may be from each date and still be used, in days. Default 30, max 3650.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 load and does well: it discloses the source archives consulted, that captures are snapped to the nearest date with the gap reported, that comparison is text-level only, and the changed:false semantics for identical or restyled captures. It omits failure behavior when no capture falls within the tolerated gap and any rate/size limits.

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

Conciseness3/5

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

Front-loading the question is good and the body is dense with useful facts, but the final sentence is cut off mid-word ('with the reason (sa'), leaving an incomplete clause that costs clarity. Otherwise there is little filler.

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?

No output schema exists, so the description must describe return values and it largely does: removed/added segments, similarity score, both capture timestamps and their gaps, plus the changed flag with reasoning. What is missing is the no-capture/error path, which matters for a tool whose success depends on third-party archive coverage.

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% and all four parameters are already documented, including date formats and the max_gap_days default/max, so the baseline of 3 applies. The description reinforces the intent of the two dates (earliest vs. latest capture to resolve) but adds no syntax or edge-case detail beyond the schema.

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?

Names a specific verb+resource ('What changed on a web page between two dates?') and then spells out the mechanism: resolving the nearest archived capture from Wayback, Common Crawl and Arquivo.pt, extracting readable text of both, and diffing. That is far more than a restatement of the name and lets an agent tell this apart from a generic evidence/compare sibling.

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

Usage Guidelines4/5

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

The opening question establishes the use case clearly, and the note that it diffs readable text rather than markup tells the agent when the result will be misleading (restyled pages report changed:false). It stops short of naming an alternative tool or stating explicit when-not-to-use conditions, so it is clear context without full routing 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.