Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

ssl_scan

Analyze a host's SSL/TLS configuration to identify certificate details, supported protocols, ciphers, and potential security weaknesses on a specified port.

Instructions

Analyze SSL/TLS configuration of a host

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>"
    },
    "name": "ssl_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesTarget hostname
portNoPort number

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?

No annotations are provided, so the description carries the full burden. It does not disclose whether the scan is passive or intrusive, what specific SSL/TLS properties are checked (ciphers, protocols, certificate expiry), expected runtime, or whether it requires network access. 'Analyze' implies a read-only operation but this is not explicitly stated.

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, front-loaded sentence with no wasted words. It is efficient but perhaps overly terse given the complexity of the operation.

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?

With no annotations, no output schema, and a very short description, there is insufficient context about what the analysis returns, how it behaves, or what an agent should expect. For a security scanning tool, this leaves significant gaps in understanding.

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 description coverage is 100%, so the input schema already documents both 'host' and 'port' with clear descriptions. The tool description adds no additional meaning beyond what the schema provides, which is the baseline expectation when schema coverage is complete.

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 states a specific verb ('Analyze') and resource ('SSL/TLS configuration of a host'), making the tool's purpose clear. It does not explicitly differentiate itself from siblings like nmap_scan, but the SSL/TLS focus is specific enough that an agent can distinguish it.

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 guidance on when to use this tool versus alternatives such as nmap_scan or nikto_scan, nor any prerequisites or exclusions. The implied usage is inferable from the purpose, but no explicit when-to-use context is provided.

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