VERDICT

by tejcodes-rex

Overview Schema Source Related Servers Discussions Admin

Python

Local

fs_timeline

Generate a file system MAC timeline from a disk image and extract the most recent file activity for forensic analysis.

Instructions

Generate a file system MAC timeline body and parse the most recent activity (fls -m + mactime).

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": {
      "image": "<image>"
    },
    "name": "fs_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`image`	Yes
`offset`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It implies a read-only 'generate' operation but does not state whether any modifications occur, what constitutes 'most recent activity,' or output format details. The output schema exists but the description adds no behavioral context.

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?

The description is a single sentence with no wasted words. However, it could be restructured to front-load key information; currently it ends with technical details (fls -m + mactime) that may be opaque to some agents.

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?

Despite having an output schema, the description lacks essential context such as the type of input image required, the meaning of the offset parameter, and how this differs from super_timeline. The tool is under-documented for an agent to use correctly without additional inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides no explanation for the two parameters ('image' and 'offset') despite 0% coverage in the schema. The agent must guess that 'image' is a disk image path and 'offset' is a sector offset, which are not self-evident without domain knowledge.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it generates a MAC timeline using fls -m and mactime, identifying a specific forensic operation. It distinguishes the tool from other file system tools like fs_list or fs_cat that have different purposes.

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?

No explicit guidance on when to use this tool versus siblings. There is no mention of prerequisites, alternatives, or contexts where this tool is appropriate, leaving the agent to infer usage from the name alone.

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