Skip to main content
Glama
Sign In
NetOps MCP Server

NetOps MCP Server

by drew-1618
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

run_ping

Check network reachability by pinging an IP or hostname. Get average latency and packet loss to diagnose connectivity issues.

Instructions

Pings an IP address or hostname to check reachability, average latency, and packet loss.

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": {
      "target": "<target>"
    },
    "name": "run_ping"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral disclosure burden. It states the operation and the metrics returned, implying a read-only diagnostic, but it does not mention permissions, timeouts, packet size, or whether any state changes occur. For a simple ping this is adequate but not rich.

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 with no filler; the key facts (action, target type, result metrics) are front-loaded. Every phrase contributes information.

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?

The description is sufficient to understand what the tool does, and the stated metrics hint at the response contents despite the absence of an output schema. However, the count parameter is unspecified and no usage exclusions or operational caveats are provided, so an agent must still guess at edge cases.

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 coverage is 0%, so the description must compensate. It defines 'target' as an IP address or hostname, but it does not describe 'count', leaving the agent to infer that it controls the number of probes. This is only partial compensation for the schema gap.

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 the verb 'Pings' and specifies the resource ('an IP address or hostname') and the outcome ('reachability, average latency, and packet loss'). It is clear and distinct from sibling tools in practice, but it never explicitly contrasts with resolve_dns or the telemetry tools, so it stops short of the top score.

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

Usage Guidelines3/5

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

The purpose clause 'to check reachability, average latency, and packet loss' implies when the tool is useful, but there is no explicit when-to-use or when-not-to-use guidance. Sibling tools like resolve_dns and get_gateway_telemetry exist, yet the description does not route the agent among them.

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