ssh-mcp-pro

Port Check

port_check

Read-onlyIdempotent

Identify processes listening on a given port to diagnose network conflicts and security issues.

Instructions

Checks which processes are listening on a specific port

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": {
      "sessionId": "<sessionId>",
      "port": "<port>"
    },
    "name": "port_check"
  }
}

Input Schema

Name	Required	Description
`host`	No	Host to check (default: 127.0.0.1)
`port`	Yes	Port number to check (1-65535)
`sessionId`	Yes	SSH session ID

Output Schema

Name	Required	Description	Default
`code`	Yes
`stderr`	Yes
`stdout`	Yes
`durationMs`	Yes
`safetyWarning`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.5Jun 28, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint (false), indicating a safe, idempotent operation. The description adds no additional behavioral details, such as error handling, performance characteristics, or limits, failing to go beyond what annotations provide.

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

Conciseness5/5

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

The description is a single, information-dense sentence with no redundant words. It is front-loaded with the core action and resource, making it efficient for quick understanding.

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

Completeness4/5

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

Given the presence of an output schema, the description does not need to elaborate on return values. It adequately covers the tool's primary function. However, it could mention that it requires an SSH session (sessionId) for context, which is implied but not explicit.

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 parameter meanings are already documented. The description does not add extra context beyond the schema, such as expected formats or behavior for edge cases (e.g., invalid port). Baseline score applied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('Checks') and resource ('processes listening on a specific port'). It uniquely identifies the tool's purpose among siblings, as no other sibling tool explicitly checks listening ports.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparisons with sibling tools like net_interfaces or ssh tools, leaving the agent without contextual decision-making support.

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