Skip to main content
Glama
Sign In
chungus-kali-mcp

chungus-kali-mcp

by cryptopepy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

forensics_volatility

Analyze memory dumps for forensic artifacts and malicious activity using Volatility3.

Instructions

Memory forensics with Volatility3.

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": {
      "memory_file": "<memory_file>"
    },
    "name": "forensics_volatility"
  }
}

Input Schema

NameRequiredDescriptionDefault
pluginNowindows.info
memory_fileYes
additional_argsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It says nothing about executing Volatility3 plugins, read-only vs. mutating behavior, output format, or any side effects. This is a severe transparency gap for a complex memory forensics tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is very short with no waste, but it is under-specified. It provides no more information than the tool name, so the single sentence does not earn its place. This is under-specification, not good conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of Volatility3 (many plugins, arguments, and output types), the absence of parameter details, usage guidance, and output schema makes the description wholly incomplete. An agent cannot correctly select or invoke this tool based on the provided information.

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 schema has 0% description coverage and no parameter descriptions. The description does not compensate by explaining memory_file, plugin, or additional_args. The parameter semantics are entirely undocumented, leaving the agent without any meaning beyond parameter names.

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

Purpose2/5

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

The description 'Memory forensics with Volatility3' restates the tool name (forensics_volatility) and adds only the terms 'memory' and '3'. It lacks a specific verb or action, and does not differentiate from sibling forensics tools like forensics_strings or forensics_binwalk. This is closer to a tautology than a clear purpose.

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?

The description provides no guidance on when to use this tool versus the many sibling tools. It does not mention scenarios, prerequisites, alternatives, or exclusions. With no usage context, an agent cannot determine when selecting this tool is appropriate.

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

Deploy Server

Other Tools