Skip to main content
Glama

Wayback

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Snapshot

get_snapshot
Read-onlyIdempotent

Look up the archived/historical version of a web page in the Internet Archive Wayback Machine. Returns the closest available snapshot (its Wayback URL, timestamp and HTTP status). Pass a timestamp to find the snapshot nearest a specific date; omit it to get the latest archived version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe page URL to look up, e.g. "example.com" or "https://example.com/page".
timestampNoOptional target date as YYYYMMDD or YYYYMMDDhhmmss. The closest snapshot to this time is returned. Defaults to the latest snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://example.com"
+  },
+  {
+    "timestamp": "20200101",
+    "url": "https://example.com/page"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and not destructive. The description adds behavioral context: it returns the 'closest available' snapshot (not exact) and specifies the returned fields (URL, timestamp, status).

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, no unnecessary words, front-loaded with the core action. Every sentence adds value.

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

Completeness5/5

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

For a simple lookup tool with no output schema, the description adequately explains the return value (Wayback URL, timestamp, HTTP status). It is complete enough for an agent to use.

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 covers both parameters. Description adds semantics by explaining the effect of including/excluding the timestamp parameter, going beyond the schema's type and format hints.

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?

The description clearly states the tool retrieves an archived web page from the Internet Archive Wayback Machine, specifying the verb (look up) and resource (archived version). It distinguishes from sibling tools by focusing on historical snapshots.

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?

It explains when to include the timestamp parameter (to get snapshot near a specific date) and when to omit it (get latest). While it doesn't explicitly list exclusions, the context is clear for this tool's single purpose.

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

All Wayback toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources