Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose a fair amount: multi-source fallback, HTML stripping, that the returned capture may not be the exact date, and that the gap is reported. It does not disclose latency, rate limits, authentication, or what happens when no archive holds a capture — the final sentence that would address exactly that is truncated.

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 motivating question, then a dense but well-organized sentence covering sources, processing, and return payload. Nearly every clause carries information; the dangling final fragment is wasted space and signals the text was cut off.

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 4-parameter read tool with no output schema, the description covers far more than most: output fields (text, timestamp, link, gap), default and max limits are in the schema, and the multi-source fallback is explained. The truncated closing sentence leaves the no-capture outcome undefined, which is the one material 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 coverage is 100%, so url, date, max_chars and max_gap_days are all documented in the schema itself, putting this at the baseline. The description's gap discussion adds conceptual meaning to max_gap_days (captures farther than that are rejected), which is a modest but real addition beyond the schema.

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?

Opens with a concrete question ("What did a web page say on a given date?") then names the resource (an archived capture of a URL) and the sources it draws from (Wayback, Common Crawl, Arquivo.pt). It is specific enough that an agent knows exactly what this does; the only missing piece is explicit differentiation from the sibling archive_compare, which is not mentioned (possibly in the truncated tail).

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?

The framing question establishes the use case (retrospective page content at a point in time), and "One call replaces the find-capture, fetch-record, parse-HTML chain" steers agents away from a multi-step manual approach. No explicit when-not-to-use or named alternative tool is given; the sentence about the no-archive case is cut off mid-word, so the failure-path guidance is unavailable.

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.