Skip to main content
Glama
Socialpranker

netops-mcp

by Socialpranker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

TCP port check

tcp_port_check
Read-onlyIdempotent

Check whether specific TCP ports on a host accept connections. Perform a TCP-level port verification without HTTP or TLS checks.

Instructions

Check whether specific TCP ports on a host accept connections. This is a connectivity check of named ports — NOT a discovery scan. Capped by scope-guard. Use this when you need to verify a SPECIFIC port is open at the TCP level. It does NOT send HTTP or check TLS. Use after net_ping confirms the host is alive, or when ICMP is blocked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYestarget host
portsYeslist of ports to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint, idempotentHint, destructiveHint; description adds behavioral constraints like scope-guard cap and that it doesn't send HTTP or check TLS, adding value beyond annotations.

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?

Five concise sentences, each with distinct information, front-loaded with purpose, no fluff.

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

Completeness5/5

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

Covers purpose, limitations, usage context, and ordering relative to siblings; no output schema needed, complete for its complexity.

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 covers both parameters with descriptions (100% coverage), so description adds minimal extra meaning beyond the main purpose; baseline 3 is appropriate.

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?

Description clearly states it checks TCP ports on a host for connectivity, distinguishes from siblings by specifying it's not a discovery scan and doesn't check HTTP or TLS.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (verify a specific port is open), when not to use (not a discovery scan, doesn't check HTTP/TLS), and provides context (use after net_ping or when ICMP blocked).

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