Wayback Check

wayback_check

Read-onlyIdempotent

Check if a URL was archived and retrieve the closest snapshot. Returns capture dates and direct link to the archived version.

Input Schema

Name	Required	Description	Default
`url`	Yes	The URL to look up (e.g., "https://example.com/some-page")

Output Schema

Name	Required	Description
`url`	Yes	The queried URL
`status`	Yes	Status code of the snapshot
`archived`	Yes	true = a capture exists; false = the capture index was asked and holds none; null = could not determine (see reason)
`timestamp`	Yes	Timestamp of the closest snapshot
`snapshot_url`	Yes	Direct URL to the archived snapshot

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedOutput schema / properties / archived / description

Previous value: -"Whether the URL has been archived"New value: +"true = a capture exists; false = the capture index was asked and holds none; null = could not determine (see reason)"

changedOutput schema / properties / archived / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "archived": {
+      "description": "Whether the URL has been archived",
+      "type": "boolean"
+    },
+    "snapshot_url": {
+      "description": "Direct URL to the archived snapshot",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Status code of the snapshot",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "timestamp": {
+      "description": "Timestamp of the closest snapshot",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "The queried URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "archived",
+    "snapshot_url",
+    "timestamp",
+    "status"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "url": "https://example.com/some-page"
+  },
+  {
+    "url": "https://www.cnn.com/2001/09/11/"
+  }
+]

First observedApr 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent, open-world lookup, so the safety profile is covered. The description adds useful behavior beyond that: it resolves to the closest snapshot and returns capture dates plus a direct link, which tells the agent what to expect from the call. It doesn't mention limits (e.g., missing archives, coverage gaps), so it stops short of rich behavioral context.

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, front-loaded with the core action, followed by return-value expectations. Nothing is wasted or repeated from structured fields.

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?

For a one-parameter read-only lookup with a full output schema and rich annotations, the description covers what the tool does and what comes back. It stops short of mentioning how it relates to the other archive tools, which is the only meaningful gap.

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 100% and the single parameter is fully documented in the schema with an example. The description adds no extra meaning about URL format, normalization, or edge cases, so the baseline 3 applies.

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?

The description names a specific verb and resource (check whether a URL was archived, retrieve the closest snapshot), so an agent knows exactly what the tool does. It does not, however, distinguish itself from sibling tools like archive_compare or archive_evidence.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The closest thing to guidance is implied by the purpose statement (checking archive existence), which the agent could infer from any sibling archive tool.

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

All Archive tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.