Skip to main content
Glama

LinkVet

Find an archived copy (Wayback Machine)

wayback_snapshot
Read-onlyIdempotent

Find the Internet Archive Wayback Machine snapshot of a URL closest to a date (or the latest). Returns snapshot_url and time. Use it to cite a dead page (when check_url says 404) or to show what a page said at a past date.

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": "wayback_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to look up
timestampNoOptional target date, YYYYMMDD or YYYYMMDDhhmmss: returns the closest snapshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, and idempotent, so the safety profile is covered; the description adds the return shape (snapshot_url and time) and the closest-match selection behavior. It stops short of saying what happens when no snapshot exists or how far back the archive reaches, which is a meaningful edge case for an open-world lookup.

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 sentences, both earning their place, with the core behavior front-loaded and the usage trigger following. No redundant restatement of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the returned fields, and it covers the primary use cases. The remaining gap is failure behavior when the archive has no capture for the URL, which matters for an open-world tool an agent may call speculatively.

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, but the description adds meaning the schema lacks: that omitting the timestamp yields the latest snapshot (the schema only says "optional"). It does not add format detail beyond what the schema's YYYYMMDD pattern already provides.

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 ("Find the Internet Archive Wayback Machine snapshot of a URL") plus the selection rule (closest to a date, or the latest). It also implicitly distinguishes itself from check_url, so an agent can tell what this tool does without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions: cite a dead page when check_url returns 404, or show what a page said at a past date. It names the sibling tool and the exact trigger that selects this one over it.

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.

Resources