Skip to main content
Glama

ping

Read-only

Tests IPv4/IPv6 reachability from the MikroTik router by sending ICMP or ARP probes, helping verify connectivity and path MTU before troubleshooting.

Instructions

Pings an IPv4/IPv6 address or host name from the router (needs the "test" policy).

Notes: interval: e.g. "200ms" or "1s". arp_ping=True sends ARP requests instead of ICMP and needs interface. do_not_fragment with size finds the path MTU.

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

Input Schema

NameRequiredDescriptionDefault
ttlNo
sizeNo
countNo
deviceNo
addressYes
arp_pingNo
intervalNo
interfaceNo
src_addressNo
routing_tableNo
do_not_fragmentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.29.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=false. The description goes beyond them usefully by naming the required policy and by explaining that arp_ping switches from ICMP to ARP and demands an interface, and that do_not_fragment+size performs path-MTU discovery. That is meaningful added behavior, but it remains silent on defaults such as count=4 or on how results are reported.

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 main sentence is front-loaded and the prerequisite is stated parenthetically, which works. The "Notes:" block is terse but reads as a fragment dump with trailing whitespace and no ordering principle, so it is efficient rather than well-structured.

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?

An output schema exists, so return-value explanation is not owed. For an 11-parameter diagnostic tool the description covers the non-obvious switches (arp_ping, do_not_fragment, interval) and the auth prerequisite, leaving only the more self-descriptive fields (ttl, count, src_address) unexplained.

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 coverage is 0% across 11 parameters, so the description must carry the load; it explains only interval (format examples), arp_ping (with its interface dependency) and do_not_fragment (paired with size for MTU discovery). Seven-plus parameters — ttl, device, src_address, routing_table, count, address — get no meaning beyond their titles.

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?

States a specific verb and resource: "Pings an IPv4/IPv6 address or host name from the router." The scope (from the router, IPv4/IPv6, address or hostname) is precise enough to distinguish it from route/DNS/interface siblings, though no explicit sibling alternative is named.

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?

Adds a real prerequisite — the "test" policy is required — which is genuine when-to-use context. It does not, however, say when to prefer this over related diagnostics like check_route_path, nor when not to use it.

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