Skip to main content
Glama

ping

Read-onlyIdempotent

Check if the Minestom MCP server is reachable by sending an optional message and receiving an echo response.

Instructions

Use this when you want to verify that the Minestom MCP server is reachable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNoOptional text to echo back in the response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
echoedMessageYes
okYes
timestampYes

Implementation Reference

  • The ping tool handler function that parses input, echoes a message (or 'pong'), and returns an ok status with a timestamp.
    export const pingTool: TanStackServerTool = toolDefinition({
    	description:
    		"Use this when you want to verify that the Minestom MCP server is reachable.",
    	inputSchema: pingInputSchema,
    	name: "ping",
    	outputSchema: pingOutputSchema,
    }).server(async (args) => {
    	const { message } = pingInputSchema.parse(args);
    
    	return pingOutputSchema.parse({
    		echoedMessage: message ?? "pong",
    		ok: true,
    		timestamp: new Date().toISOString(),
    	});
    });
  • Input schema for the ping tool: accepts an optional 'message' string to echo back.
    const pingInputSchema = z.object({
    	message: z
    		.string()
    		.optional()
    		.describe("Optional text to echo back in the response."),
    });
  • Output schema for the ping tool: returns echoedMessage, ok boolean, and timestamp string.
    const pingOutputSchema = z.object({
    	echoedMessage: z.string(),
    	ok: z.boolean(),
    	timestamp: z.string(),
    });
  • src/tools.ts:18-28 (registration)
    Registration of pingTool into the serverTools array alongside other tools.
    tools.push(
    	pingTool,
    	createGetServerInfoTool(toolNames),
    	inspectMinestomEnvironmentTool,
    	inspectMinestomBuildTool,
    	explainMinestomPatternTool,
    	lookupMinestomApiTool,
    	planMinestomFeatureTool,
    	reviewMinestomDesignTool,
    	suggestMinestomLibrariesTool,
    );
Behavior5/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds the specific behavior of verifying reachability and echoing an optional message, which is consistent and adds context beyond the annotations.

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 that is concise and front-loaded with the purpose. Every word is necessary and there is no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature of the tool, the presence of an output schema (indicated by context), and comprehensive annotations, the description provides complete context for an AI agent to understand when and how to invoke it.

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 schema has 100% description coverage for the single optional parameter 'message', so the baseline is 3. The tool description does not add any new information about the parameter beyond what the schema already provides.

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 clearly states the verb 'verify' and the resource 'Minestom MCP server reachability', making it distinct from sibling tools like 'get_server_info' or 'inspect_minestom_build'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use the tool ('verify that the Minestom MCP server is reachable'), but does not provide explicit when-not-to-use or alternatives. However, the context is clear and sufficient for basic guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Azoraqua/minestom-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server