Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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/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 burden and does substantial work: it discloses the multi-archive search strategy, that HTML is stripped to readable text, and the exact return payload (text, capture timestamp, archive link, and the gap between requested and actual capture). What it does not cover is the failure path — the final sentence breaks off at "If no archive holds a cap", so the agent cannot tell whether a miss raises an error, returns empty, or widens the search.

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?

The lead question is an effective front-load and most sentences are dense and purposeful. However, the definition is visibly truncated mid-word ("If no archive holds a cap"), leaving a dangling fragment that wastes space and signals an incomplete definition rather than a deliberately short one.

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, fully-documented schema with no output schema, the description covers the essentials: what it searches, what it returns, and how the returned capture may differ from the requested date. The one material hole is the truncated tail that would have explained behavior when no archive holds a capture near the date — an agent needs that to handle misses.

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 already documented in the schema, which sets the baseline at 3. The description does add conceptual meaning to the gap concept ("the GAP between the date asked for and the capture actually used", with a day-count example), which indirectly explains what max_gap_days controls, but it adds no format or default 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?

Opens with a concrete question ("What did a web page say on a given date?") and then names the specific verb and resource: finds the archived capture of a URL nearest a date, reads it, and returns stripped text. It also names the three sources (Wayback, Common Crawl, Arquivo.pt) and explicitly positions itself against the find-capture/fetch-record/parse-HTML chain, so an agent can distinguish it from a simple fetch tool.

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 opening question plus "Finds the archived capture of a URL nearest that date" gives a clear condition for use, and "One call replaces the find-capture, fetch-record, parse-HTML chain" tells the agent to prefer this over multi-step alternatives. There is no explicit "when not to use" and no routing to a sibling such as archive_compare, 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.