Skip to main content
Glama
Sign In
mcp-archive

mcp-archive

by jeffereychown-Max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

archive_url

Submit any URL to the Wayback Machine for immediate archiving and receive the snapshot URL back.

Instructions

Submit a URL to be archived right now by the Wayback Machine. Returns the snapshot URL once captured.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to archive (http/https)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided; the description only mentions return of the snapshot URL. It does not disclose side effects, rate limits, authentication needs, or whether the archiving is synchronous. The statement 'right now' hints at immediacy but lacks specificity.

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?

The description is a single sentence that efficiently conveys the tool's purpose and result, with no superfluous content.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, no output schema), the description is minimally adequate but lacks information on preconditions (e.g., URL accessibility), idempotency, or error handling.

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%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter description, and no additional validation or format hints are given.

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 action ('Submit a URL to be archived right now') and the resource ('Wayback Machine'), with a distinct purpose from siblings that focus on retrieval or comparison.

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 description implies immediate archiving but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. Usage is inferred from the sibling tools' different purposes.

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

Deploy Server

Other Tools