Skip to main content
Glama

hello

Verifies the GitHub MCP server is operational by returning a confirmation response.

Instructions

A simple test tool to verify that the MCP server is working correctly

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'hello' tool handler registered directly on the McpServer. It takes no parameters and returns a JSON response with a greeting message and timestamp, verifying MCP server connectivity.
    server.tool(
    	"hello",
    	"A simple test tool to verify that the MCP server is working correctly",
    	{},
    	async () => ({
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify({
    					message: "Hello from GitHub MCP Server!",
    					timestamp: new Date().toISOString(),
    				}, null, 2),
    			},
    		],
    	}),
    )
  • src/index.ts:22-37 (registration)
    The 'hello' tool is registered via server.tool() call inside registerAllToolsAndResources(). No separate schema file exists; the empty object {} is passed as the schema.
    server.tool(
    	"hello",
    	"A simple test tool to verify that the MCP server is working correctly",
    	{},
    	async () => ({
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify({
    					message: "Hello from GitHub MCP Server!",
    					timestamp: new Date().toISOString(),
    				}, null, 2),
    			},
    		],
    	}),
    )
  • The schema for 'hello' is an empty object {}, meaning the tool accepts no parameters.
    {},
Behavior4/5

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

No annotations provided, so description carries full burden. It accurately indicates the tool is for verification with no side effects, which is sufficient for a zero-parameter ping-like tool.

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?

Single sentence, no redundant words. Perfectly concise for a simple tool.

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?

Given the tool's trivial nature (0 params, no input), the description is complete enough. However, no output schema means the return value is unclear, but for a test tool this is acceptable.

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?

No parameters exist, schema coverage is 100%. Description adds no additional parameter info, but none is needed. Baseline 4 is appropriate.

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 it is a test tool to verify the MCP server works, using a specific verb 'verify' and resource 'MCP server'. This distinguishes it from all sibling tools which are functional GitHub operations.

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?

No explicit guidance on when to use or not use this tool, but the simplicity implies it is for initial connectivity checks. Lacks exclusion criteria or alternative references.

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/hithereiamaliff/mcp-github'

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