Skip to main content
Glama

usn_events

Retrieves an inode's $UsnJrnl:$J records ordered by USN, exposing FileCreate, BasicInfoChange, and Rename contradictions for timestomping and rename/move analysis.

Instructions

Return one inode's $UsnJrnl:$J change-journal records ordered by USN (the attacker-independent clock). Surfaces FileCreate/BasicInfoChange/Rename contradictions.

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": "<inode>"
    },
    "name": "usn_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
inodeYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/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. It does disclose real behavior beyond the name: results are ordered by USN, scoped to a single inode, and oriented toward surfacing contradictions between event classes. It says nothing about what happens for an inode with no journal records, whether the journal is sparse, or whether the limit truncates silently.

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?

Two dense sentences with zero filler, front-loaded with the verb and scope. The parenthetical about the 'attacker-independent clock' earns its place by explaining why USN ordering matters forensically.

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 two-parameter read tool with no output schema, the description covers purpose and ordering but leaves return-shape expectations and limit behavior unspecified. Adequate to start a call, thin for interpreting results.

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%, so the description must compensate for both parameters. It clarifies that 'inode' selects a single inode's journal, but 'limit' (default 64) is never mentioned, leaving the agent with no idea that results may be truncated or how to page through a long journal.

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 specific verb ('Return') and a precise resource ('one inode's $UsnJrnl:$J change-journal records') plus the ordering key, so an agent can tell this is a per-inode journal read rather than a global carve or an MFT dump. It never names a sibling explicitly, so the differentiation is implicit rather than stated.

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?

There is no explicit when-to-use or when-not guidance and no named alternative, but 'Surfaces FileCreate/BasicInfoChange/Rename contradictions' implies the investigative scenario this serves. The agent must still infer that this is the follow-up step after identifying an inode of interest.

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