Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__archive_evidence

What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy, and the GAP between the date asked for and the capture actually used (e.g. "Captured 1.5 day(s) before the requested date"). One call replaces the find-capture, fetch-record, parse-HTML chain. If no archive holds a cap

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.sec.gov",
      "date": "2023-06-01"
    },
    "name": "nplg-catalog__archive_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page address, e.g. "https://www.sec.gov" or "https://www.ftc.gov/policy-notices/privacy-policy".
dateYesThe date to look up, as YYYY-MM-DD (e.g. "2023-06-01"), YYYYMMDD, or a full ISO timestamp.
max_charsNoCharacters of page text to return. Default 12000, max 60000.
max_gap_daysNoFurthest a capture may be from the 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?

No annotations are supplied, so the description carries the full burden and mostly meets it: it discloses that multiple archives are queried, that HTML is stripped, that the capture timestamp and archived link are returned, and that a gap value quantifies how far the capture is from the requested date. The significant remaining gap is failure behavior, since the sentence beginning 'If no archive holds a cap' is truncated and never states what happens when nothing is found, nor whether there are 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 core question and the mechanism, then layers on return values and the consolidation benefit, with no filler. It loses a point because the final sentence is truncated mid-word ('holds a cap'), leaving an incomplete thought in the text an agent reads.

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, so the description correctly spends its space explaining what is returned: readable text, capture timestamp, archive link, and the gap. For a four-parameter read tool this is nearly complete, with the only shortfall being the unresolved no-capture behavior at the truncated end.

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 all four parameters are already documented, establishing a baseline of 3. The description adds meaning to the gap concept and its example output, which indirectly explains max_gap_days, but it does not add format or syntax detail for url or date beyond what the schema already provides.

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 and names a specific verb+resource: find the archived capture of a URL nearest a date, reading it and returning stripped text. It enumerates the three sources (Wayback, Common Crawl, Arquivo.pt) and the exact outputs, so an agent can distinguish it from siblings such as archive_compare 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?

It gives a clear selection signal by stating this single call replaces the find-capture, fetch-record, parse-HTML chain, which tells an agent to prefer it over a multi-step approach. It does not name an alternative sibling tool or state when NOT to use it, and the closing sentence about the no-capture case is cut off before the fallback behavior is described.

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.