Skip to main content
Glama
nucleusv

Linux MCP daemon

by nucleusv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

network/ping

Read-onlyIdempotent

Test TCP reachability (not ICMP) by opening one connection to a host and port, then closing it. Returns success, latency, and error details for connectivity checks.

Instructions

Tests TCP reachability: opens one TCP connection to host:port and closes it. This is NOT ICMP, so it needs a listening port (default 80) and says nothing about other ports or ICMP. Single attempt, no loss statistics; latency includes DNS resolution. Read-only, but it connects off-host and honors the user's network: policy in mcp-sudo.yaml. timeout is whole seconds (default 5). A failed connect is not a tool error: the JSON has success: false and an error text. Returns JSON with host, port, success, latency_ms and error. For DNS only use network/nslookup, for the hop path network/trace-path, for an HTTP check network/curl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesHostname or IP address to connect to
portNoTCP port, whole number (default 80)
timeoutNoSeconds, whole number (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.1
    • addedInput schema / properties / host / description
      Added value: +"Hostname or IP address to connect to"
    • changedInput schema / properties / port / description
      Previous value: -"Defaults to 80"New value: +"TCP port, whole number (default 80)"
    • addedInput schema / properties / timeout / description
      Added value: +"Seconds, whole number (default 5)"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond annotations: notes it connects off-host, honors the user's network: policy in mcp-sudo.yaml, that failure is not a tool error but a JSON success:false, that latency includes DNS, and that it is a single attempt with no loss statistics. Annotations only signal read-only/idempotent/open-world; the description adds the operational realities an agent needs.

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?

Dense but front-loaded: behavior, caveats, then sibling routing. Nearly every clause earns its place, though it is information-heavy in one paragraph and could be split for scanability.

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?

For a 3-param network probe with no output schema, it covers return fields (host, port, success, latency_ms, error), the failure model, policy interaction, and alternatives. Nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds non-obvious semantics the schema omits - port defaults to 80 because a listening port is required, timeout is whole seconds with default 5, and failure semantics attach to the connect result. Adds meaning beyond the schema wording.

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?

States a specific verb and resource ('Tests TCP reachability: opens one TCP connection') and explicitly disambiguates from ICMP. It names four siblings (nslookup, trace-path, curl) with the condition selecting each, so an agent can route without opening schemas.

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?

Explicit when-to-use routing ('For DNS only use network/nslookup, for the hop path network/trace-path, for an HTTP check network/curl') plus when-not ('This is NOT ICMP'). Covers alternatives and scope exclusions directly.

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