Skip to main content
Glama
rmschn

MCP Simple Example

by rmschn

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
network-pingA

Send ICMP echo requests to a host to test connectivity and measure latency.

USE CASES:
- Check if a host is reachable over the network
- Measure round-trip time (latency) to a host
- Diagnose network connectivity issues
- Verify if a firewall is blocking ICMP traffic

WHAT IT DOES:
- Sends multiple ICMP echo request packets to the target host
- Waits for echo response packets
- Reports packet loss percentage and response times

PARAMETERS:
- host: Required. The hostname or IP address to ping (e.g., 'google.com', '8.8.8.8')
- count: Optional. Number of ping packets to send (default: 4)

OUTPUT:
- Packet loss statistics
- Min/Avg/Max response times
- Will show '100% packet loss' if host is unreachable or blocking ICMP
network-tracerouteA

Trace the route that packets take to reach a destination host.

USE CASES:
- Identify network path between source and destination
- Diagnose where network latency is occurring
- Find broken or slow network hops
- Understand network topology for debugging

WHAT IT DOES:
- Sends packets with increasing TTL (Time To Live) values
- Each router along the path decrements TTL and returns its IP
- Shows all intermediate hops between your machine and target

PARAMETERS:
- host: Required. The hostname or IP address to trace (e.g., 'cloudflare.com')
- max_hops: Optional. Maximum number of hops to trace (default: 30)
- timeout: Optional. Seconds to wait for each hop response (default: 5)

OUTPUT:
- List of all hops (routers) along the path
- IP address of each hop
- Round-trip time for each hop
- Shows '* * *' for hops that don't respond

NOTE: On Windows, this command is called 'tracert' instead of 'traceroute'

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: ping tests reachability and latency, while traceroute maps the network path. There is no realistic confusion between them.

Naming Consistency5/5

Both tools follow the same network-<command> naming pattern, making the set predictable and easy to navigate. The consistency holds across both tools.

Tool Count3/5

With only two tools, the server feels thin, but the pair of ping and traceroute forms a natural, coherent unit for basic network diagnostics. It is slightly under the typical well-scoped range but not unreasonable for a simple example server.

Completeness4/5

For basic network troubleshooting, ping and traceroute cover the two most common diagnostic needs: connectivity/latency and route/path analysis. A DNS lookup or port check would be a minor enhancement, but the current surface is not severely incomplete for the implied scope.

Maintenance

ActivityMaintained
ResponsivenessNo issues