Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__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": "nist-standards__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

A3.8/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 behavioral burden and mostly does: it discloses multi-source fan-out, HTML stripping, that the returned capture may not be exactly the requested date, and that the gap is reported explicitly. It also signals a gap-limiting constraint. However, the final sentence is truncated ('If no archive holds a cap'), so the no-capture/failure behavior is left incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is front-loaded with the motivating question and wastes little in the middle, but the trailing sentence is cut off mid-word ('If no archive holds a cap'), which is both wasted space and a loss of information. The parenthetical example of the gap message is useful; the truncation is a real structural defect.

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 must explain returns — it does: readable text with HTML stripped, capture timestamp, link to the archived copy, and the date gap. That covers what an agent needs to interpret results. The incomplete final sentence leaves the no-archive-holds-a-capture case unspecified, which is the main remaining gap.

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, max_chars and max_gap_days are already documented in the schema. The description reinforces the gap concept with an example ('Captured 1.5 day(s) before the requested date') and mentions readable text, which loosely maps to max_chars/max_gap_days, but adds no format or syntax detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description leads with a concrete question ('What did a web page say on a given date?') and then names the specific operation: finding the nearest archived capture of a URL across Wayback Machine, Common Crawl and Arquivo.pt and returning the readable text. That is a specific verb-plus-resource statement an agent can act on. It does not explicitly distinguish itself from the sibling nist-standards__archive_compare, so it falls short of a 5.

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 clear usage context: use this to retrieve page content as of a date, and 'One call replaces the find-capture, fetch-record, parse-HTML chain' tells the agent this is the consolidated path rather than a multi-step pipeline. No explicit when-not-to-use condition or named alternative is given, so it stops short of a 5.

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.