Skip to main content
Glama
Example MCP Server

Example MCP Server

by Ranjith63812

ping

Verify server availability by sending a health check request that returns 'pong', confirming the MCP server is running and responsive.

Instructions

A simple health check tool that returns 'pong'

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ping"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It usefully discloses the response payload ('pong'), which is the main behavioral fact for a health check, but says nothing about latency, failure behavior, or whether any authentication is needed. For a trivial read-only probe this is sufficient but not rich.

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?

One short sentence, front-loaded with the tool's classification and ending with the concrete return value. No wasted words and nothing an agent must read past to find the key fact.

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?

For a tool of this complexity, the description covers both purpose and return value, and there is no output schema that would otherwise explain results. The only missing element is any note about failure or error behavior, which is minor for a ping probe.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty schema and the description are consistent. Baseline 4 applies for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ('health check') and states the exact return value ('pong'), so an agent knows precisely what the tool does. It is trivially distinguishable from the contextual siblings (file_reader, git_status, system_info), which all operate on system state rather than acting as a liveness probe.

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?

Usage is only implied: the phrase 'health check' signals when to call it (verifying connectivity or server availability), but there is no explicit when-to-use/when-not-to-use guidance or named alternative. For a zero-argument liveness probe the implied usage is close to self-evident, so this is adequate rather than deficient.

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