Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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 supplied, the description carries the full disclosure burden and does it well: it names the three upstream sources, states the capture-selection rule (nearest capture within max_gap_days), discloses the return payload (removed/added segments, similarity score, both capture timestamps plus their gap from requested dates), and explains the changed:false path for identical or same-text captures. Remaining gaps are operational details such as behavior when no capture exists within the allowed gap and any rate or 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.

Conciseness4/5

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

The description is front-loaded with the user-facing question, then moves through mechanism, output shape, and the important text-vs-markup caveat, with no filler sentences. It loses a point because the text is truncated mid-clause ('...with the reason (sa'), leaving a dangling sentence that wastes space and breaks structure.

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 moderately complex four-parameter tool with no output schema and no annotations, the description covers the mechanism, sources, and result fields an agent needs to interpret the response. The truncated tail is the only substantive completeness defect; otherwise nothing critical to correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns a bump by explaining the semantics behind the date parameters: each date is resolved to the nearest capture, and the response reports 'both capture timestamps with their gaps from the requested dates', which contextualizes the max_gap_days tolerance rather than merely restating it. It does not add format or syntax detail beyond the schema, so it is not a 5.

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?

The description opens with a concrete question ('What changed on a web page between two dates?') and then names the exact verb pipeline: resolve the nearest archived capture from Wayback/Common Crawl/Arquivo.pt, extract readable text, and return a text-level diff. This is specific enough that an agent can tell it apart from a generic archive-lookup tool such as archive_evidence without inspecting schemas.

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 two-date framing and by the explicit caveat that it diffs text rather than markup, so an agent knows when the tool is inappropriate (CSS/markup-only changes). However, it never names an alternative sibling or states exclusions such as 'use X instead for raw capture retrieval', so the routing guidance is inferred rather than explicit.

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.