Skip to main content
Glama

NovaPixel LexGrid

port_leak_detector

Non-invasive bounded TCP probe to identify exposed critical databases (MySQL, Postgres, Redis, MongoDB, Elastic), unauthenticated Docker daemon and admin ports with SSRF protection.

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": {
      "hostname": "<hostname>"
    },
    "name": "port_leak_detector"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesTarget domain or public IP address to inspect
timeoutMsNoPer-port socket connect timeout in milliseconds (500-3000ms)
customPortsNoOptional list of specific custom ports to probe (max 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real context beyond the name — 'non-invasive bounded', 'SSRF protection', and the implication that probing is capped — but it never states whether results are cached, whether probes are rate-limited, what happens on hosts that block the source, or what the response contains.

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 front-loaded sentence with zero filler; the target categories are grouped efficiently in parentheses. It is dense but readable, and nothing is wasted, though the parenthetical list makes it slightly harder to scan than a short lead clause plus detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only place an agent could learn what a result looks like — open vs closed ports, banners, or severity — and it says nothing about that. For a three-parameter network probe whose return shape is entirely undefined, that is a meaningful gap, though the input side is well covered by the schema.

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 hostname, timeoutMs (with default and 500-3000ms range), and customPorts (max 10) are already fully documented in the schema. The description adds no further meaning about parameter tradeoffs, such as how timeout affects accuracy or when customPorts should replace the default port set.

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 names a specific verb and resource ('bounded TCP probe') and enumerates exactly what it hunts for: MySQL, Postgres, Redis, MongoDB, Elastic, unauthenticated Docker daemon, and admin ports. That is far more precise than a generic port scanner, though it never distinguishes itself from the listed siblings (domain_rdap_intel, email_deliverability_audit, tls_http_inspector), which the agent must infer are different domains.

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, no named alternative, and no statement about authorization or scope of consent for scanning a host. The agent can infer the tool is a security-posture check from the enumerated targets, but nothing tells it which situation should select this tool over tls_http_inspector.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources