Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present the description carries the full load, and it does substantial work: it names the three upstream archives, explains that captures are resolved to the nearest date with gaps reported, and states that identical captures return changed:false with a reason. It omits rate limits, latency, auth needs, and what happens when no capture falls within the gap tolerance; the final sentence is also cut off mid-word, losing part of the identical-capture explanation.

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?

Information is front-loaded: the purpose question comes first, then mechanism, then the diff-semantics caveat. Sentences are dense and mostly earn their place, but the trailing sentence is truncated mid-word, leaving a dangling fragment that undercuts an otherwise tight 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 four-parameter tool with no output schema and no annotations, the description covers inputs, upstream data sources, the shape of the result (removed/added segments, similarity score, capture timestamps and gaps, changed flag), and the key false-negative mode. Missing pieces are the no-capture-within-gap case and the incomplete final sentence.

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%, so url, date_a, date_b, and max_gap_days are already documented, including the default of 30 and max of 3650. The description reinforces the meaning of the gap by saying results include each capture's timestamp and its gap from the requested date, but adds no format or constraint 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?

The opening question plus the follow-on sentence name a precise verb and resource: resolve the nearest archived capture to each of two dates from named archives (Wayback, Common Crawl, Arquivo.pt), extract readable text, and return a text-level diff with a similarity score. An agent can distinguish this from evidence-gathering siblings 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 implied by the framing (compare a page across two points in time) and one important caveat is stated: it diffs readable text, not markup, so cosmetic restyling yields changed:false. There is no explicit when-not-to-use guidance and no routing to alternatives such as archive_evidence for a single-capture or evidence-style lookup.

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.