Skip to main content
Glama

Domain history (Wayback)

domain_history
Read-onlyIdempotent

Internet Archive history for a domain or page URL: first and latest snapshots (with view links), snapshot/month counts, unique pages, years active, status-code mix, yearly timeline, a short former-use title check (casino/adult/pharma/loan flags), and Spamhaus DBL status. Read-only. Free.

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

Input Schema

NameRequiredDescriptionDefault
domainYesdomain or page URL, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so 'Read-only' in the description mostly repeats structured data. 'Free' is genuinely new context (no credit/cost implications) and naming Spamhaus DBL hints at external lookups. However, nothing is said about behavior for never-archived domains, whether counts are approximate, latency, or caching, so the added behavioral depth is modest.

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?

One front-loaded sentence puts the resource first and then lists outputs efficiently, with the qualifiers ('Read-only. Free.') trailing. The middle enumeration is dense but each item earns its place by telling the agent what data it will get back. Minor cost: the comma-separated list is long enough to skim poorly.

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?

There is no output schema, so the description correctly compensates by itemizing the return payload, including the caveat that the former-use check is 'short' and flag-based. For a single-parameter read-only lookup this is close to sufficient; only failure modes and richness of the title/Spamhaus checks remain unstated.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains it ('domain or page URL, e.g. example.com'). The description's 'domain or page URL' phrasing mirrors the schema rather than adding normalization rules or accepted URL forms. Baseline 3 applies when the schema does the heavy lifting.

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 resource (Internet Archive/Wayback history) and enumerates exactly what is returned: snapshots, counts, years active, status-code mix, timeline, title flags, and Spamhaus DBL status. That makes it easy to distinguish from siblings like estimate_domain_value or search_domains. It stops short of an explicit 'use this instead of X' statement, so a 4 rather than 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?

No explicit when-to-use, when-not, or alternative guidance is given; the agent must infer that this is the Wayback/archive-lookup option from the enumerated outputs. Usage is implied rather than stated, which is the definition of a 3.

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