mcp-ping
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Pings a host and returns the result |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so no possibility for confusion. The tool's purpose is clearly distinct.
With a single tool, naming consistency is inherently perfect. The verb-style name matches the action.
A single tool is minimal, but for a dedicated ping utility it is acceptable and not excessive. It borders on thin but works for its narrow purpose.
The tool covers the core functionality of pinging a host. Given the server's apparent single-purpose scope, there are no obvious missing operations.