Skip to main content
Glama

enumerate_mft

Scores clean-but-active inodes from a read-only $MFT scan to prioritize triage; a high score flags candidates for review, not a verdict.

Instructions

Score 'clean-but-active' candidate inodes worth triaging (read-only $MFT scan). A high score is a reason to triage, never a verdict.

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": "enumerate_mft"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filterNocandidate filter; 'clean-but-active' is the default heuristicclean-but-active

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description still earns credit for disclosing that the scan is read-only and for the interpretive caveat that a high score is 'a reason to triage, never a verdict'. It does not explain what the heuristic measures, whether results are ordered by score, or how limit truncation interacts with ranking.

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 operation and scope, with no filler. The first sentence is dense and slightly awkward in phrasing ('Score "clean-but-active" candidate inodes worth triaging'), but no sentence is wasted.

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 scoring tool with no output schema and no annotations, the description never says what a result contains (inode, score, rank order) or how to read the score scale. An agent knows the intent but not what it will receive or how to act on it.

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 coverage is only 50%: 'filter' is documented in the schema itself, and 'limit' has no description anywhere. The description adds nothing about what other filter values exist, what the limit bounds, or how ordering works, so it fails to compensate for the coverage 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 concrete resource ($MFT) and a concrete operation (scoring candidate inodes for triage), which separates it from siblings like carve_residual_usn or vol_mft_memory. The verb 'Score' does not match the tool name 'enumerate_mft', leaving mild ambiguity about whether the primary output is a list or a ranking.

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 explicit when-to-use or when-not-to-use guidance and no sibling is named as an alternative. The phrase 'worth triaging' hints at the triage-prioritization context, but an agent gets no criteria for choosing this over reconstruct_timeline or usn_events.

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