Skip to main content
Glama
Sign In
HALO (GEMMA-by-GOOGLE)

HALO (GEMMA-by-GOOGLE)

by XenoCoreGiger31
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

run_netstat

List active network connections and listening sockets to identify open ports and running services for network reconnaissance.

Instructions

List network connections and listening sockets (falls back to 'ss').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_netstat"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNonetstat/ss flags.-tuln

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions a fallback to 'ss' but lacks details on permissions, output format, or side effects.

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?

One sentence with no wasted words. Could be slightly more structured but is efficient and to the point.

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 no output schema and minimal annotations, the description is insufficient. Lacks return value information, usage context, and fails to explain how results are presented.

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% for the single parameter, so baseline is 3. The description does not add significant meaning beyond the schema's 'netstat/ss flags.'

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 clearly states it lists network connections and listening sockets, with a fallback to 'ss'. It provides a specific verb and resource, but could better distinguish from sibling network tools like run_nmap.

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?

No guidance on when to use this tool versus alternatives. The description does not include when-not-to-use or mention any prerequisites.

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