Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

netcat_connect

Connect to a target host and port using netcat to grab service banners and identify exposed network services.

Instructions

Connect to a host and port using netcat for banner grabbing

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": {
      "host": "<host>",
      "port": "<port>"
    },
    "name": "netcat_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesTarget host
portYesTarget port

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 and mostly fails to meet it. It does not say whether the connection is read-only, whether any payload is sent, how long it waits, whether it can hang on a silent service, or what form the returned banner takes — all critical for an agent invoking netcat against an arbitrary host.

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?

A single compact sentence with the purpose front-loaded and no filler. It is efficiently worded, though the brevity comes at the cost of the behavioral detail an unannotated tool needs.

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 an unannotated tool with no output schema and a raw network connection, the definition leaves too much unsaid: timeout behavior, what is returned, error handling on refused or filtered ports, and side effects on the target. The agent knows what to send but not what to expect back.

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%, so 'host' and 'port' are already documented as 'Target host' and 'Target port' in the schema itself. The description restates the parameters without adding format details, defaults, or constraints, so baseline 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?

States a specific verb (connect), the resource (host and port), and the mechanism/purpose (netcat for banner grabbing), which sets it apart from scanning siblings like nmap_scan or nikto_scan. It stops short of explicitly naming which sibling to prefer, but an agent can tell what this tool is for.

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?

The phrase 'for banner grabbing' implies the intended use case, so guidance is present but only implicit. There is no explicit when-to-use versus when-to-use-something-else guidance, no mention of when a service-specific tool would be better, and no prerequisites such as the target needing an open port.

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