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

first_seen

Find the earliest archived snapshot of a website to discover when it was first captured by the Wayback Machine.

Instructions

Find the earliest archived snapshot of a website.

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>"
    },
    "name": "first_seen"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and gives almost nothing beyond the one-line purpose. It does not say what happens when a site has no archived snapshot, whether the archive source is fixed, whether results are cached, or whether the call can be slow or rate-limited for popular URLs.

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?

A single front-loaded sentence with no filler, and the defining qualifier 'earliest' is placed where it reads first. Nothing is redundant, though there is very little substance to structure.

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?

An output schema exists, so return values needn't be explained, and the tool has just one simple parameter. Still, for an external-archive lookup the description omits the empty-result case and URL format expectations, which are the two things an agent most needs to call it correctly and interpret the response.

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

Parameters2/5

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

Schema description coverage is 0% for the single required url parameter, and the description only hints that it is 'of a website.' It adds no format guidance such as whether a full URL with scheme, a bare domain, or a specific path is expected — a meaningful ambiguity for archive lookup tools.

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 earliest archived snapshot of a website.' The word 'earliest' distinguishes it from a generic snapshot or history listing, so an agent can tell what makes it unique, though it never names snapshot or history explicitly.

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?

Usage is only implied — you use it when you need the oldest capture. There is no statement of when to prefer it over snapshot or history, and no note on whether history should be called first to discover dates. Adequate but leaves the routing decision to inference.

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