Skip to main content
Glama
Sign In
PenTest MCP

PenTest MCP

by anishxagrawal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

testssl

Checks TLS/SSL configurations of a target host to identify security weaknesses and misconfigurations.

Instructions

TLS/SSL security testing

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

Input Schema

NameRequiredDescriptionDefault
hostYes
portNo
dry_runNoPreview commands/steps without executing the scan
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

C2.3/5.0
Behavior1/5

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

No annotations provided and the description gives no behavioral traits (destructiveness, permissions, output characteristics). The agent has no insight into side effects or requirements.

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

Conciseness3/5

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

The description is a single sentence, which is concise but minimal. It lacks structure and does not earn its place by adding value beyond the name.

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 tool's four parameters, lack of output schema, and presence of a similar sibling tool, the description is severely insufficient. It does not explain return values, prerequisites, or how it differs from 'sslyze'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% (only 'dry_run' has a description). The tool description adds no meaning to parameters like 'host', 'port', or 'session_id', failing to compensate for the low coverage.

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 clearly states the tool performs TLS/SSL security testing, which is specific. However, it does not differentiate from sibling tool 'sslyze' which also tests SSL/TLS.

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 on when to use 'testssl' versus alternatives like 'sslyze' or other scanning tools. No when-to-use or when-not-to conditions provided.

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