Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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 load and does well: it explains capture resolution per date, the max-gap tolerance, which archives are consulted, that the diff is text-level rather than markup, and the changed:false semantics for identical captures. It omits failure behavior when no capture exists, and the text is truncated mid-sentence, which costs some transparency.

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 the core question, then the mechanism, then the return shape and the key caveat, which is the right ordering. It is dense but each sentence carries information; the trailing truncation is the only structural flaw.

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 tool with no output schema, the description does the needed work by describing the returned diff segments, similarity score, capture timestamps, and changed flag. The one meaningful hole is behavior when an archive has no capture near a requested date, which is hinted at but cut off.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all four parameters at 100% coverage, so the baseline is 3, but the description adds real meaning by explaining what the gap between a requested date and the resolved capture represents, which directly clarifies max_gap_days beyond its schema wording. It adds nothing about date ordering or URL format beyond what the schema examples already give.

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 a concrete question that names the resource (a web page) and the operation (diff between two dates), then specifies the sources (Wayback, Common Crawl, Arquivo.pt) and the output shape. An agent can distinguish this from sibling compare tools like compare_entities without opening the schema.

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?

Usage is strongly implied by the description's framing (comparing a page across two dates) and the caveat that it diffs readable text, not markup, tells an agent when results will look misleading. However, no alternative tool or explicit when-not-to-use condition is named, so routing to archive_evidence or compare_entities is left to inference.

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.