Skip to main content
Glama

reconstruct_timeline

Rebuild a USN-ordered timeline for a set of inodes and emit a deterministic tri-state verdict; pass supersedes_step to mark a self-correction.

Instructions

Rebuild the true timeline ordered by USN for an inode set and emit the deterministic tri-state verdict. Pass supersedes_step to mark a self-correction.

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": {
      "inode_set": "<inode_set>"
    },
    "name": "reconstruct_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_byNoUSN
inode_setYesinodes to place on the USN-ordered timeline
supersedes_stepNothe earlier step this verdict overturns (self-correction)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

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 two valuable traits: the output is deterministic (stable tri-state verdict) and re-runs can overturn a prior step via supersedes_step. It does not say whether the tool is read-only or mutates stored state, what the three verdict states actually are, or how missing/unknown inodes are handled.

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 sentences, front-loaded with the core action and output, with no filler. It is dense with domain jargon, which costs a bit of readability but no sentence is wasted.

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 three-parameter tool with no annotations and no output schema, the definition covers the action and output shape but leaves the verdict semantics, data prerequisites, and read-vs-write nature unstated. Adequate to attempt a call, not complete enough to predict what it returns.

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 coverage is 67% and the schema already documents inode_set and supersedes_step, both of which the description largely restates. The one undocumented parameter, order_by, is only implicitly referenced through the "ordered by USN" phrasing, so the description adds little beyond the structured fields.

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?

Uses a specific verb (Rebuild) with a named resource (timeline), a scope (an inode set, USN-ordered) and an output (a deterministic tri-state verdict). Domain jargon like "true timeline" and "tri-state verdict" is left undefined, and nothing distinguishes it from siblings such as usn_events or carve_residual_usn, so it stops 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 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 reach for this tool versus usn_events, carve_residual_usn, or the other MFT tools, nor any preconditions (e.g. that USN data must already be collected). The only guidance is a parameter note about supersedes_step, which is invocation mechanics rather than usage selection.

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