Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

metasploit_exploit_info

Get detailed information about a specific Metasploit module from its full path to review exploit details before penetration testing.

Instructions

Get detailed information about a specific Metasploit module

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": {
      "module": "<module>"
    },
    "name": "metasploit_exploit_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
moduleYesFull module path (e.g., exploit/windows/smb/ms17_010_eternalblue)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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. "Get" implies a read-only lookup, but it does not state what kind of detail is returned (options, targets, references), what happens for an invalid or unknown module path, or whether any Metasploit instance must be running.

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?

One front-loaded sentence with no filler, and the key object of the call appears immediately. Its brevity is efficient, though it is short partly because content is missing rather than because it is dense.

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?

There is no output schema and no annotations, so the description is the only source of information about what the call returns and how it behaves. For a detail-lookup tool, omitting the shape of the returned module information leaves an agent unable to predict the result or handle failures.

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 already documented with a concrete full-path example, so the schema does the heavy lifting. The description adds only that the path names "a specific Metasploit module," which is a baseline-3 contribution rather than new meaning.

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 pairs a specific verb ("Get detailed information") with a specific resource ("a specific Metasploit module"), so the operation is unambiguous. It stops short of distinguishing this lookup from the sibling metasploit_search, which is the main clarity gap.

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. An agent can only infer that this is the follow-up to a search once a module path is known; the description never names metasploit_search as the discovery alternative or states the prerequisite of a valid module path.

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