Skip to main content
Glama

find_archive

Read-only

For up to 10 URLs (e.g. dead links), find the closest Internet Archive Wayback Machine snapshot, optionally nearest a date (YYYY, YYYY-MM or YYYY-MM-DD). Returns snapshot URL, capture time, captured status. Price: 0.005 USDC per call (x402, 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": {
      "urls": "<urls>"
    },
    "name": "find_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDefault target date
urlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the return payload (snapshot URL, capture time, captured status) and, importantly, the paid-call cost of 0.005 USDC per call via x402 on Base — real operational context an agent needs. It does not say what happens when no snapshot exists, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: capability and limit first, return values second, cost last. No filler or redundant restatement of the tool name.

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 supplies the return shape and the payment requirement, which covers most of what an agent needs. The one meaningful gap is behavior on a miss (no snapshot captured), which affects result interpretation.

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

Parameters5/5

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

Schema coverage is only 50%, and the description compensates by specifying the accepted date formats (YYYY, YYYY-MM, YYYY-MM-DD) and the nearest-match semantics for the otherwise terse "Default target date" parameter. It also restates the 10-URL cap tied to maxItems, adding usable meaning beyond the schema.

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 closest Internet Archive Wayback Machine snapshot" for up to 10 URLs, with an optional target date. The scope (max 10, nearest-date semantics) is precise enough to act on. It does not explicitly distinguish itself from verify_links/verify_citations, so it falls 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?

The parenthetical "(e.g. dead links)" implies the intended scenario, and the optional date-nearness hints at archival-history use. However, there is no explicit when-not-to-use guidance and no named alternative among the siblings, leaving routing to inference.

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