Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.2/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 much of it: it discloses the return payload (stripped readable text, capture timestamp, archive link, and the gap between requested and actual capture) and explains that captures may precede or follow the requested date. It adds the useful note that the capture is chosen as 'nearest' rather than exact, but says nothing about rate limits, authentication, or per-archive fallback ordering, and the truncated clause leaves the no-capture failure behavior undefined.

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?

Densely front-loaded: the purpose question, the mechanism, the return shape, and the chain-replacement rationale each appear once with no filler. It loses a point only because the final sentence is truncated mid-word, leaving an unfinished clause that costs clarity rather than words.

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 research tool with no output schema and no annotations, the description covers the return shape well and the pipeline benefit well. It is incomplete on the failure path (what happens when no archive holds a capture — the very sentence that would answer this is cut off) and on cost/latency behavior of querying three archives, which an agent needs to decide whether to call it.

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; the description nonetheless adds real meaning by explaining what the 'gap' is and giving the concrete output form ('Captured 1.5 day(s) before the requested date'), which ties directly to how max_gap_days and the nearest-capture selection interact. That is meaningful semantics beyond the schema's terse field descriptions.

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 specific question ('What did a web page say on a given date?') and then states the concrete operation: find the nearest archived capture of a URL across Wayback Machine, Common Crawl and Arquivo.pt, read it, and return text. The scope (three specific archives, nearest-to-date selection) makes it distinguishable from generic fetch or search tools in a way an agent can act on immediately.

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?

Gives a clear routing rule: 'One call replaces the find-capture, fetch-record, parse-HTML chain,' telling the agent to prefer this over multi-step retrieval. There are no explicit exclusions or when-not-to-use conditions, and the trailing sentence on the no-archive case is cut off, so the boundary conditions are only partly stated.

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.