Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

check_ports

Read-only

Lists all listening TCP ports and associated processes on a specified server to identify open services and resolve port conflicts.

Instructions

List all listening TCP ports and associated processes on a server.

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": {
      "server": "<server>"
    },
    "name": "check_ports"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful scoping (TCP listeners plus owning processes), but says nothing about privilege requirements (many listeners are only visible with elevated rights), IPv4/IPv6 or UDP exclusion, or result volume on a busy host. It is consistent with the annotations, not contradictory.

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?

One sentence, front-loaded with the verb and resource, with zero filler. Every word contributes to scope.

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?

For a simple one-parameter read tool with no output schema and clear read-only annotations, the core is covered. Missing pieces — how to identify the server, privilege caveats, and whether UDP/IPv6 are included — are modest but real gaps for an agent that must call it correctly on the first try.

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 0% for the single required "server" parameter, so the description must carry the burden. It only implies targeting via "on a server" and never states whether the value is a hostname, IP, or an alias from list_servers, nor whether the target must be connected first.

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 uses a specific verb and resource ("List all listening TCP ports and associated processes") and scopes it explicitly to TCP listeners, which is narrower and more precise than a generic port scan. It does not, however, distinguish itself from plausible siblings such as firewall_status or process_list, so an agent must infer the boundary.

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 when-to-use guidance, no when-not-to-use, and no named alternative. An agent cannot tell from the text whether to prefer this over firewall_status (rules) or process_list (all processes) when diagnosing a connectivity problem.

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