Windows Developer MCP Server

Overview Schema Source Related Servers Discussions Admin

ping

Send ICMP echo requests to a hostname or IP address and return round-trip statistics, enabling connectivity testing and latency measurement.

Instructions

Ping a host and return round-trip statistics.

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

Name	Required	Description	Default
`host`	Yes	The hostname or IP address to ping.
`count`	No	Number of ping packets to send (1–10). Default: 4.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states the action and result, but omits details such as network requirements, potential timeouts, or failure behavior. It provides only minimal transparency into what the tool actually does beyond the obvious.

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 sentence, front-loads the core action, and contains no filler. It is appropriately concise for the tool's simplicity.

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?

Given the low complexity, simple schema, and presence of an output schema, the description is minimally sufficient. However, it lacks usage context and behavioral notes, which are relevant for an agent deciding between network diagnostic tools. The description could be more complete with a sentence on when to use it or its limitations.

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?

The input schema provides 100% coverage for both parameters (host and count) with descriptions and default. The description adds no extra parameter semantics beyond the schema, so it meets the baseline but does not enhance understanding of parameter usage.

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 'Ping a host and return round-trip statistics' clearly states the action (ping) and resource (host), and hints at the output (round-trip statistics). It is specific enough to distinguish from siblings like traceroute, though it doesn't explicitly name alternatives.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention context like checking host reachability or compare with traceroute/dns_lookup. This leaves the agent without explicit selection criteria.

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

Deploy Server