Skip to main content
Glama
time-machine-mcp
by Prashan7h

snapshot

Find the archived version of a website closest to a specified date via the Wayback Machine, letting you see how a page looked on or near that date.

Instructions

Find the archived snapshot of a website closest to a given date. Date format YYYYMMDD, YYYYMM or YYYY.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "date": "<date>"
    },
    "name": "snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden. It usefully discloses the non-obvious near-match behavior ('closest to a given date') rather than implying an exact-date lookup, but it says nothing about what happens when no snapshot exists, how large the tolerance window is, or any access constraints. The output schema covers return values, which offsets part of the gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero waste; the core action is front-loaded and the format constraint follows as a secondary spec.

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?

The output schema handles return values, so the description needn't explain results. However, for a two-parameter tool with no annotation coverage and no schema descriptions, it should at minimum clarify URL format and the no-match/approximate-match outcome; both are missing.

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 0% (only bare titles 'Url' and 'Date'), so the description must compensate. It does define accepted date formats (YYYYMMDD, YYYYMM, YYYY), which is genuinely useful, but leaves 'url' entirely unexplained — no indication of whether a scheme, host, or path is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find the archived snapshot of a website') plus the selection rule ('closest to a given date'), which distinguishes it from a full listing. It does not explicitly differentiate from the siblings first_seen or history, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'closest to a given date' implies the use case (retrieve a capture near a point in time), but there is no explicit when-to-use guidance, no statement of when another tool such as history or first_seen would be preferable, and no mention of prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools