Skip to main content
Glama
time-machine-mcp
by Prashan7h

history

Lists one archived website snapshot per year across a specified date range so you can compare how the site changed over time.

Instructions

List one archived snapshot per year for a website, to see how it changed over time.

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>",
      "from_year": "<from_year>",
      "to_year": "<to_year>"
    },
    "name": "history"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
to_yearYes
from_yearYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 one meaningful behavioral trait: the result is sampled to one snapshot per year, not every capture. 'List' implies a read-only operation. It does not say what happens for years with no captures, whether results are ordered, or whether the call is rate-limited.

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?

A single front-loaded sentence with no filler; the purpose and the sampling behavior are both in the first clause. It is efficient, though its brevity is partly under-specification rather than pure tightness.

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

Completeness2/5

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

The output schema covers return values, so that gap is excused, but for a three-required-parameter tool with zero schema descriptions the definition says nothing about input formats or edge cases. An agent could form the right intent yet still call it incorrectly (e.g., wrong URL form or an exclusive year range).

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

Parameters2/5

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

Schema description coverage is 0% across three required parameters, and the description never mentions url, from_year, or to_year. It does not clarify URL format (scheme/host vs. bare domain), whether the year range is inclusive, or how out-of-range years are handled, leaving the agent to guess at all three inputs.

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 ('List one archived snapshot per year for a website') with the intent ('see how it changed over time'), which distinguishes it from a single-snapshot tool. It stops short of naming or contrasting with the siblings snapshot/first_seen, so differentiation is inferential rather than explicit.

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 purpose clause ('to see how it changed over time') implies the use case: longitudinal/trend inspection rather than retrieving a specific capture. There is no explicit when-not guidance, no mention of when to prefer snapshot or first_seen, and no stated prerequisites (e.g., whether the site must exist in the archive).

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