Skip to main content
Glama
Sign In
Geekflare

Geekflare

Official
by geekflare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

openPorts

Check which ports are accessible on a target URL for security audits and network diagnostics. Customize scans by selecting top ports or specifying custom ranges.

Instructions

Scan open ports on 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": {
      "url": "<url>"
    },
    "name": "openPorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget URL
topPortsNoScan top N ports
portRangesNoCustom port ranges e.g. 80,443,1000-1010

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.4

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not address whether the scan is safe, destructive, rate-limited, or reveals any side effects, leaving agents uninformed about potential risks or constraints.

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 concise sentence with no extraneous information. While it is short, it is appropriately front-loaded and objectively efficient.

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?

Given the absence of annotations and output schema, the description should provide more context about the scan behavior, output format, and potential impact. It is too brief to adequately prepare an agent for invocation.

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 coverage is 100% with descriptions for all three parameters. The tool description does not add extra meaning beyond the schema, meeting the baseline expectation for high-coverage parameters.

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 'Scan open ports on a host' uses a specific verb and resource, clearly distinguishing this tool from sibling tools that focus on web scraping, DNS, or HTTP checks. However, it could be more precise about the scope (e.g., a single host vs. network).

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 alternative network scanning tools or under what conditions (e.g., permission needed). No exclusions or prerequisites are mentioned.

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