Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.1/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 most of it: it names the three upstream archives, explains capture selection by nearest date, and describes the response shape (removed/added segments, similarity score, capture timestamps and their gaps from requested dates). It also discloses the key semantic caveat that restyling without word changes yields changed:false, and hints at a reason field for identical captures — though the sentence is truncated, leaving that behavior only partly specified.

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?

The question is front-loaded, followed by mechanism, output shape, and the text-vs-markup caveat in a tight sequence with little filler. It is dense but every clause carries information; the only real defect is the truncated final sentence, which leaves a dangling fragment.

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?

There is no output schema, but the description adequately characterizes the return payload (diff segments, similarity score, timestamps, gaps), which is the main thing an agent needs. Gaps remain around failure behavior — no capture within max_gap_days, unavailable archives, or invalid URLs — and the truncation cuts off the identical-capture explanation.

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%, including formats and the max_gap_days default and cap, so the schema does the heavy lifting. The description reinforces that dates drive nearest-capture resolution and that a similarity score plus timestamp gaps are returned, but it adds no format or constraint detail beyond the schema. Baseline 3 is appropriate.

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?

Opens with the exact user question it answers and then states the concrete mechanics: resolving nearest archived captures across Wayback, Common Crawl, and Arquivo.pt, extracting readable text, and returning a text-level diff with similarity score and timestamps. The verb+resource+output are all specific enough to distinguish it from siblings like archive_evidence or recent_changes without opening a schema.

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 framing 'What changed on a web page between two dates?' establishes the use case clearly, and the note that it diffs readable text rather than markup tells the agent when a changed:false result is trustworthy versus misleading. It stops short of naming an alternative tool or stating when not to use this one (e.g., for markup/CSS changes), so it falls just below the explicit when/when-not bar.

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.