Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

domain_wayback_availability

Get the closest Wayback snapshot for a domain via a single Internet Archive Availability API request, useful for checking archived availability quickly.

Instructions

Get the closest Wayback snapshot. Performs one Internet Archive Availability API request.

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": {
      "domain": "<domain>"
    },
    "name": "domain_wayback_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesBare DNS hostname

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that this is a single external Internet Archive request, which signals network latency and rate-limit exposure. It omits what happens when no snapshot exists (error vs. empty result), whether results are cached, and that the call is read-only only by implication of 'Get'.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence is terse enough to be slightly cryptic, but it does convey real information about upstream cost.

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?

For a one-parameter lookup this is close to adequate, but with no output schema and no annotations the description leaves the return shape entirely unknown (timestamp? URL? archived content?). It also does not cover the no-snapshot case, which is the main branch an agent must handle.

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?

Only one parameter exists and the schema documents it fully as 'Bare DNS hostname' at 100% coverage, so the baseline applies. The description adds no meaning beyond the schema, such as whether schemes, subdomains, or URLs with paths are rejected.

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 concrete verb and resource: 'Get the closest Wayback snapshot' for a domain, which is unambiguous and separable from the sibling CDX listing tool. It stops short of explicitly naming the sibling it differs from.

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 statement of when to use this versus domain_wayback_cdx or when not to use it. The closest available guidance is the implicit notion of 'closest snapshot', which an agent must infer selects the nearest capture to now.

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