Skip to main content
Glama
Sign In
NetOps MCP Server

NetOps MCP Server

by drew-1618
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_gateway_telemetry

Discover the local default gateway and verify first-hop reachability to diagnose network connectivity issues.

Instructions

Discover the local default gateway and check first-hop reachability.

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": "get_gateway_telemetry"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 the full burden. It discloses the operation (discover gateway, check first-hop reachability) but does not mention whether this is a read-only operation, whether it requires special permissions, what the output looks like, or whether it performs any active network probes that could have 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the primary action ('Discover the local default gateway') and adds the secondary purpose ('check first-hop reachability'). No wasted words.

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 zero-parameter tool with no output schema, the description is reasonably complete for basic invocation. However, it lacks information about the return format, whether the check is active or passive, and how it relates to run_ping. An agent could call it correctly but may not know what to expect from the result.

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?

The tool has zero parameters, so the schema provides no parameter semantics. The description appropriately explains what the tool does without needing to document parameters. Baseline 4 is appropriate for a zero-parameter tool.

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 states a specific verb ('Discover') and resource ('local default gateway'), and adds 'check first-hop reachability' to clarify the telemetry aspect. It is clear enough to distinguish from siblings like get_wifi_telemetry, though it does not explicitly name a sibling.

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 description implies a diagnostic/network-checking use case, and the sibling list includes run_ping and resolve_dns, so an agent can infer this is for gateway-level reachability rather than general connectivity. However, it does not explicitly state when to use this tool versus run_ping or get_wifi_telemetry.

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