Skip to main content
Glama

mft_si_fn

Checks $STANDARD_INFORMATION against $FILE_NAME MACB timestamps for one inode to detect timestomping; equal SI/FN values are a hypothesis to test, not proof of innocence.

Instructions

Run the textbook $STANDARD_INFORMATION vs $FILE_NAME MACB check for one inode (live istat). $SI==$FN is a hypothesis to break, not innocence.

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

Input Schema

NameRequiredDescriptionDefault
inodeYesMFT entry number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only provides the analytical framing that '$SI==$FN is a hypothesis to break, not innocence.' It does not state whether the operation is read-only, what permissions are needed, what output or comparison fields are returned, or how missing entries 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two front-loaded sentences with no filler. The first sentence states the operation and scope; the second adds an important interpretive caveat without restating the name or schema.

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 specialized forensic check with no output schema and no annotations, the definition is too thin. It does not explain what the comparison returns, how to interpret results, or when to prefer this over sibling tools, leaving the agent with only the invocation parameter and a warning.

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 100% and the single parameter is documented as an MFT entry number. The description's phrase 'for one inode' reinforces the parameter's meaning but adds no format, range, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 states a specific operation: running the $STANDARD_INFORMATION vs $FILE_NAME MACB comparison for one inode using live istat. The scope ('one inode', 'live istat') helps distinguish it from siblings like enumerate_mft or memory-based MFT tools, though no sibling is explicitly named.

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?

Usage is implied by 'for one inode (live istat),' which suggests a targeted single-entry check rather than a bulk enumeration. However, there is no explicit when-to-use guidance, no when-not-to-use, and no named alternatives such as enumerate_mft or reconstruct_timeline.

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