Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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
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 lot: HTML is stripped, the nearest capture is chosen rather than an exact one, the timestamp/link/gap are returned, and max_gap_days bounds acceptance. What is missing is the failure or empty-result behavior, which is precisely what the truncated last sentence was meant to cover, plus any rate-limit or archive-availability caveats.

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 question, then the mechanism, then the return shape, then the value proposition — a sensible order for an agent skimming. The single flaw is that the text ends on an incomplete clause, leaving a dangling fragment rather than a clean close.

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 four-parameter tool with no output schema, the description does the necessary work of describing the return payload (text, capture timestamp, archive link, date gap) and the multi-archive resolution strategy. It falls short on edge cases — what happens when no capture exists within max_gap_days — which is the one behavioral question an agent would most need answered.

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 url, date, max_chars and max_gap_days are already documented with defaults and maxima. The description only adds the notion that the offset between requested and actual date is surfaced as a GAP in the response, which enriches max_gap_days slightly but does not go meaningfully 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 user question and answers it with a specific verb chain: find the nearest archived capture of a URL across three named archives, read it, and return the extracted text. The resource (web page content at a date), scope (Wayback, Common Crawl, Arquivo.pt), and delivered artifact are all unambiguous.

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 'What did a web page say on a given date?' framing plus 'One call replaces the find-capture, fetch-record, parse-HTML chain' tells an agent exactly which multi-step workflow this substitutes for. No explicit when-not-to-use case survives, however, because the final sentence on the no-archive condition is cut off mid-word ('If no archive holds a cap…').

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.