Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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?

No annotations exist, so the description carries the full burden and does substantial work: it discloses HTML stripping, the returned timestamp, an archived-copy link, and crucially surfaces the approximation behavior ("GAP between the date asked for and the capture actually used", with a worked example). What it fails to disclose is the failure path — the sentence beginning "If no archive holds a cap" is cut off, so the agent cannot tell whether a miss raises an error or returns empty results.

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?

Front-loaded with the user-facing question and dense with useful detail; each sentence except the last earns its place. The definition is materially damaged by a trailing sentence that terminates mid-word ("caps"), leaving dead text in the description.

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?

With no output schema, the description must explain return values and it does — text, timestamp, archive link, and gap. Multi-archive searching and fallback ordering add useful complexity coverage. The one real hole is the truncated miss/fallback behavior, which matters for an agent deciding whether to retry with a wider date window.

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 in the schema and the baseline of 3 applies. The description adds conceptual framing that makes `date` and `max_gap_days` interpretable — the requested date versus the capture date actually used — but adds no format or unit detail beyond the schema itself.

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 the tool answers ("What did a web page say on a given date?") and then states the specific verb+resource: finds the archived capture of a URL nearest a date across Wayback Machine, Common Crawl and Arquivo.pt, and returns readable text. An agent knows exactly what it gets back, including the capture timestamp and the gap-to-requested-date.

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?

The line "One call replaces the find-capture, fetch-record, parse-HTML chain" tells the agent to prefer this over a multi-step alternative, which is genuine usage guidance. However, it does not say when NOT to use it, does not name any sibling alternative, and gives no coverage caveats beyond the truncated closing sentence.

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.