Skip to main content
Glama

vol_mft_memory

Cross-checks disk and RAM MFT records to confirm an on-disk record was not altered after capture, helping detect timestomping and rename/move laundering.

Instructions

Volatility 3 disk-vs-RAM MFT cross-check (windows.mftscan.MFTScan). Confirms the on-disk record was not altered post-capture. Never load-bearing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vol_mft_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
inodeNo

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?

No annotations are supplied, so the description bears the full disclosure burden. It does add real behavioral context: the underlying Volatility 3 plugin and the caution that results are corroborative only ('never load-bearing'). It stops short of describing what the tool returns, how it behaves when either optional parameter is omitted, or what memory-session state it depends on.

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 compact sentences with the plugin identifier and the confirmation goal front-loaded. Every clause carries information; nothing is padding.

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?

For a tool with zero annotation coverage, no output schema, and two completely undocumented optional parameters, the description leaves invocation under-specified: an agent knows what the tool checks but not how to address the record or what state the call requires. The stated purpose is clear, but the operational picture is incomplete.

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% for both parameters ('name', 'inode') and both are optional. The description says nothing about which identifier to supply, whether both are needed, or how the pair selects the record to cross-check, so it fails to compensate for the schema gap.

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 technique and namesake plugin ('Volatility 3 disk-vs-RAM MFT cross-check (windows.mftscan.MFTScan)') and states the exact finding it establishes, which separates it from a plain MFT enumeration sibling. It does not explicitly contrast with siblings, but the 'cross-check' framing is specific enough for an agent to route to it.

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?

'Never load-bearing' implies this is corroborative rather than primary evidence, and 'confirms the on-disk record was not altered post-capture' implies the use case. However, there is no explicit when-to-use/when-not-to-use statement, no named alternative, and no stated prerequisites (e.g., an attached memory image), so usage must be inferred.

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