Skip to main content
Glama

ping

Read-onlyIdempotent

Test whether a hostname or IP is reachable and measure latency, jitter, and packet loss to diagnose slow or failed network connections.

Instructions

Ping one host (hostname or IP) to see if it is reachable, with latency, jitter and packet loss. count: 1-10 pings (default 4).

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": {
      "host": "<host>"
    },
    "name": "ping"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
countNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/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 the returned metrics (latency, jitter, packet loss) and the count range, but stays silent on timeouts, behavior against unreachable/filtered hosts, and any egress or rate constraints — the areas most likely to surprise a caller.

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, front-loaded with the action and target, then the measurement value, then the parameter constraint. Nothing is padded and no clause is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, an output schema for return values, and annotations covering safety and open-world egress, the description carries what it needs to. The residual gap is failure-mode behavior — timeout duration and what a non-response returns — which matters for an agent interpreting results.

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 0%, so the description must carry parameter meaning, and it largely does: `host` is clarified as accepting a hostname or IP, and `count` gains both a 1-10 bound and a default of 4 that the schema only partially encodes. What is missing is any statement about oversize or invalid count handling.

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?

The description names a specific verb and resource ("Ping one host (hostname or IP)"), constrains the scope to a single host, and states the outcome measured ("reachable, with latency, jitter and packet loss"). That scope plus the ping-specific metrics distinguishes it from check_port, dns_lookup and traceroute without needing to name them.

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 use case is stated ("to see if it is reachable"), so an agent can infer when to reach for it, but there is no explicit when-not guidance and no routing to the sibling tools for port-level, DNS or path diagnostics. Usage is implied rather than prescribed.

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