Skip to main content
Glama
Sign In
mem-forensics-mcp

mem-forensics-mcp

by x746b
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

memory_list_plugins

Enumerate all available analysis plugins for a memory dump, combining Rust and Volatility3 capabilities.

Instructions

List all available plugins (Rust + Vol3).

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_path": "<image_path>"
    },
    "name": "memory_list_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_pathYesPath to memory dump file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool lists, but does not describe that it reads the memory dump, whether it may be slow, or what constitutes 'available' plugins. This leaves significant behavioral aspects undefined.

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 a single, concise sentence that conveys the core purpose without any filler. The 'Rust + Vol3' detail adds value and does not bloat the text.

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?

The description is too terse for an agent to fully understand the tool's context. It does not disclose the return format, which is critical since no output schema exists, nor does it explain what 'available' means in relation to the image_path. Sibling tools exist that could confuse selection, and the description offers no differentiation.

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?

The input schema has 100% description coverage for the single parameter image_path ('Path to memory dump file'). The description adds no additional semantics 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.

Purpose5/5

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

The description uses a specific verb ('List') and resource ('available plugins'), clearly stating the tool's function. The parenthetical '(Rust + Vol3)' adds specificity about plugin types, and the action of listing is distinct from running plugins (as seen in the sibling name memory_run_plugin).

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 guidance is provided on when to use this tool versus alternatives. It does not mention that this should be used for enumeration before running plugins, nor does it contrast with sibling tools like memory_run_plugin or memory_get_status.

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