Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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": "noaa-ncei__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.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose real behavior: it queries three separate archives, strips HTML, and reports the temporal gap between the requested date and the capture actually used. It is missing the failure path (what is returned when nothing is found) because the sentence is truncated, and says nothing about rate limits or archive priority.

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 and the one-call-replaces-a-chain framing are well front-loaded and earn their place. However, the body is a single very long sentence and the final sentence is cut off mid-word ('If no archive holds a cap'), which is a structural defect rather than concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with no annotations and no output schema, the description does the heavy lifting well by naming the returned fields (text, capture timestamp, archive link, gap). The truncation leaves the no-capture fallback behavior undefined, which is exactly the case an agent most needs described before committing to a call.

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, which sets the baseline at 3. The description reinforces the gap concept that max_gap_days controls and which date formats matter, but adds no format or constraint 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 and then states a specific verb and resource: finds the nearest archived capture of a URL across three named archives, reads it, and returns the extracted text. The scope (multi-archive, nearest-date) is precise enough that an agent can distinguish it from a generic fetch tool without inspecting the 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?

Explicitly positions itself against the manual workflow ('One call replaces the find-capture, fetch-record, parse-HTML chain'), which is a clear when-to-use signal. It gives no when-not guidance and does not mention the sibling noaa-ncei__archive_compare, so the routing picture is incomplete but still usable.

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.