Skip to main content
Glama
Systems Manager

Systems Manager

Ping Host

sm_network_ping_host
Read-onlyIdempotent

Pings a host to verify network connectivity and returns response results, with an adjustable count for probe attempts.

Instructions

Ping host (sm_network_operations). Operations for network analysis

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

Input Schema

NameRequiredDescriptionDefault
hostNoHost to ping or lookup
countNoPing count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the ping is ICMP, whether it targets the local machine only, what happens with no host supplied, or how long a run takes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The text is short and front-loaded, but the second sentence ("Operations for network analysis") is pure filler that earns nothing. The parenthetical namespace duplication is also wasted space.

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?

This is a simple two-optional-parameter tool with rich annotations and no output schema, so a short description is defensible. Still, the behavior when host is omitted (default null) and the interpretation of count are unaddressed, leaving real gaps for invocation.

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%, so both parameters (host, count) are already documented in the schema. The description adds no meaning beyond that baseline, and the schema's "Host to ping or lookup" wording even introduces a lookup ambiguity the description never resolves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Ping host" names a specific verb and resource, but it only restates the tool name. The trailing "Operations for network analysis" is generic filler that could describe any of the network siblings and gives no differentiation from sm_network_dns_lookup or sm_system_get_host_record.

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 guidance on when to use this versus the several network siblings, and no exclusions. An agent must infer from the name alone whether this is the right tool for reachability checks versus name resolution.

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