Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose useful behavior: HTML is stripped, the response includes the capture timestamp, an archived-copy link, and the signed gap between requested and actual date. However, the sentence that would explain what happens when no archive holds a capture is truncated ('If no archive holds a cap'), leaving the most important failure path undisclosed.

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?

Most of the text is dense and front-loaded with the task, then the replacement-chain benefit, then return values. But the description ends mid-word and mid-sentence ('If no archive holds a cap'), which breaks the structure and leaves a dangling clause that reads as a 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 four-parameter tool with no output schema, the description does a good job describing the return payload (text, timestamp, link, gap) and the substitution for a multi-step chain. The missing tail means the no-capture outcome — critical for a tool that can legitimately find nothing — is undefined, so the definition is not fully complete.

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 all four parameters are already documented, which sets the baseline at 3. The description adds some interpretive value by explaining the 'nearest date' selection and the gap concept that underlies max_gap_days, but it adds no format or unit details 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?

States a specific verb and resource (finds the archived capture of a URL nearest a date, reads it, returns the readable text) and names the three sources it searches (Wayback Machine, Common Crawl, Arquivo.pt). The opening question frames the exact task, so an agent can distinguish it from a general search or a comparison 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?

Explicitly says 'One call replaces the find-capture, fetch-record, parse-HTML chain', which tells the agent this is the single-call substitute for a multi-step workflow. It gives clear context for using this tool, but the trailing clause that presumably covered the no-capture case is cut off, so no exclusion or fallback guidance survives.

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.