Skip to main content
Glama

Internet Archive history of a website

wayback
Read-only

Internet Archive history of a website: first and latest Wayback Machine snapshot (date and link) and how long the site has existed online. Useful for trust checks and research. Takes 1-5 s. Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real value beyond them: expected latency of 1-5 s, a free tier of 20 calls/day across free tools, and a $0.002 per-call x402/USDC-on-Base charge above that. That pricing and latency detail materially affects invocation decisions. It omits edge behavior such as what is returned when no snapshots exist, which keeps it from a 5.

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?

The purpose and returned values come first, followed by latency and then the pricing model, which is logical ordering. The billing sentences are somewhat dense but each carries operational weight for an agent deciding whether to call. No filler sentences.

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 carries the burden of describing returns, and it does so concretely (first and latest snapshot date and link, site age). It also explains the paid-call flow via the payment parameter. The missing piece is failure/empty-result behavior for sites with no archived captures, which is a plausible outcome for an archive tool.

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 both parameters (url, payment) are fully documented in the schema, including the x402 flow and the instruction to omit payment on the first call. The description adds no parameter-level meaning beyond that, so the baseline of 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 definition names a concrete verb+resource: it retrieves the first and latest Wayback Machine snapshot (date and link) plus how long the site has existed online. That is specific enough for an agent to know exactly what comes back. It does not explicitly distinguish itself from adjacent siblings such as domain_whois, which also speaks to site age, so it stops short of a 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?

'Useful for trust checks and research' gives an implied context for reaching for this tool but names no alternatives and states no when-not conditions. An agent gets a hint about intent without any routing logic against the many sibling checking tools.

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.