mcp-ping-server-giulia-ai
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Health-check do próprio servidor MCP. Retorna 'pong' se estiver vivo. |
| echoA | Devolve exatamente a mensagem recebida (útil para testar o transporte). |
| check_hostA | Faz um health-check TCP REAL de um host:porta e mede a latência. Abre uma conexão TCP de verdade e retorna se a porta está acessível e o tempo de resposta em milissegundos. |
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 3 tools
Each tool has a clearly distinct purpose: ping checks the MCP server itself, echo validates the transport layer, and check_host tests real TCP reachability to a host and port. There is no meaningful overlap or ambiguity.
The names are all lowercase, short, and readable. ping and echo follow a command-line utility style while check_host uses a verb_noun pattern, so there is a slight stylistic deviation but no conflicting conventions.
Three tools is a well-scoped set for a small ping and connectivity server. Each tool earns its place and the count is neither too thin nor bloated.
The set covers the apparent domain: MCP server health checking, transport testing, and real TCP connectivity checks with latency measurement. There are no obvious missing operations that would prevent an agent from accomplishing the intended tasks.