Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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.3/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 substantial work: it discloses multi-source fallback across Wayback/Common Crawl/Arquivo.pt, that HTML is stripped to readable text, that the nearest capture may differ from the requested date, and that the divergence is quantified. It omits permissions, rate limits, caching, and — due to truncation — what happens when no archive holds a capture.

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-loading with the user-facing question is effective and the following sentences are dense with useful detail rather than filler. However, the body is one long run-on sentence and the definition ends 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.

Completeness4/5

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

For a 4-parameter, zero-annotation, no-output-schema tool, the description covers what it returns and where the data comes from, which is the hard part. The missing piece is the truncated no-capture branch — an agent cannot tell whether a miss returns null, an error, or the closest capture outside the gap threshold.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by framing the gap concept (capture date vs. requested date) that motivates max_gap_days, and by establishing that returned text length is bounded, which contextualizes max_chars. The url and date parameters themselves are not expanded beyond what the schema already documents.

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?

The description opens with a concrete verb+resource framing ("Finds the archived capture of a URL nearest that date") and names all three sources it searches, then states the return payload exactly: readable text with HTML stripped, capture timestamp, archived-copy link, and the capture-date gap. It also positions the tool against an implied workflow by saying it replaces the find-capture, fetch-record, parse-HTML chain, so an agent can tell what this does that a raw fetch would not.

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?

Usage context is clear: use this when you need to know what a page said on a specific date, and it explicitly substitutes for a three-step find/fetch/parse chain. There is no explicit "do not use when" and no named sibling contrast (e.g. archive_compare), and the sentence that likely contained the no-capture fallback guidance is cut off.

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.