Skip to main content
Glama

Ping

ping
Read-only

Send ICMP echo requests through the Keenetic router to a hostname or IPv4 address, with configurable packet count and source interface, and return the collected output.

Instructions

Send ICMP echo requests to a hostname or IPv4 address through the router. Supports a configurable packet count and source interface, and returns the collected ping output.

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
source_interfaceNoAny existing Keenetic interface name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: configurable packet count, source interface, and that it returns collected ping output (important with no output schema). It omits failure/timeout behavior and whether the call blocks, which matters for a network probe.

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?

A single front-loaded sentence covering purpose, options, and return value with essentially no waste. Slightly dense packing of three ideas into one sentence is the only minor structural weakness.

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 three-parameter, read-only probe with no output schema and partial schema coverage, the description covers purpose, options, and a rough return shape. It leaves gaps on runtime behavior (duration, timeouts, unreachable-host results) that an agent would want before invoking a network probe.

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 only 33% (only source_interface is documented in-schema). The description partially compensates by naming the packet count and source interface roles and by clarifying that host may be a hostname or IPv4 address, but it adds no bounds, defaults, or format details for host or count beyond the schema itself.

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 gives a specific verb+resource ("Send ICMP echo requests to a hostname or IPv4 address") and scopes it ("through the router"), which an agent can distinguish from traceroute. It stops short of explicitly contrasting itself with the traceroute sibling, so it is clear but not fully differentiated.

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 when-to-use guidance, no mention of when to prefer traceroute or get_internet_status instead, and no stated preconditions (e.g., reachability, permissions). The agent must infer usage entirely from the tool name and purpose sentence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.