Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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 burden and does substantial work: it names the three archive sources, discloses that captures are chosen by proximity with gaps from the requested dates, describes the return shape, and explains that identical captures return changed:false with a stated reason. Gaps remain — it does not say what happens when no capture falls within max_gap_days, nor whether it queries archives in a fallback order or rate-limits.

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-loads the core question, then layers resolution method, return contents, and the text-vs-markup caveat in a sensible order with no filler sentences. It is dense but every sentence carries information; the trailing fragment is cut off mid-clause ("with the reason (sa"), which costs a point on presentation.

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 four-parameter, no-annotation, no-output-schema tool, the description covers inputs, resolution logic, and a detailed picture of the returned fields, so an agent can call it without opening anything else. The missing pieces are the failure path when no capture is near enough and the archived-source priority; the truncated final clause may have covered the latter.

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 url, date_a, date_b, and max_gap_days are each documented with format and example in the schema itself. The description adds the concept of date-range comparison and capture proximity but never mentions max_gap_days, so it contributes no meaning beyond the structured fields. Baseline 3 applies when the schema does the heavy lifting.

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 chain — resolves the nearest archived capture on each of two dates across named archives, extracts readable text, and returns a text-level diff. The opening question plus the enumerated outputs (removed/added segments, similarity score, both capture timestamps with gaps) make it unmistakable what the tool does and how it differs from a markup diff or a generic search.

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?

Gives a clear usage frame (comparing the same URL across two points in time) and an explicit scope caveat: it diffs readable text, not markup, so a restyled page yields changed:false. That is a genuine when-not-to-trust condition. It stops short of naming an alternative such as archive_evidence or recent_changes for cases where the caller wants capture metadata rather than a diff, so routing is implied rather than spelled out.

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.