Skip to main content
Glama
snoopdave

Hello World MCP Server

by snoopdave

helloTool

Echo messages or return default greetings through the Hello World MCP Server's basic demonstration tool for testing and validation purposes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNoMessage to echo back. If not provided, returns a default greeting.

Implementation Reference

  • The asynchronous handler function that executes the helloTool logic, processing the optional message input and returning a text response or error.
    async ({ message }) => {
      try {
        const responseMessage = message ? `You said: ${message}` : "Hello, World!";
        
        return {
          content: [
            {
              type: "text",
              text: responseMessage
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error in hello tool: ${error instanceof Error ? error.message : String(error)}`
            }
          ],
          isError: true
        };
      }
    }
  • The input schema for helloTool, defining an optional 'message' string parameter using Zod.
    {
      message: z.string().optional().describe("Message to echo back. If not provided, returns a default greeting.")
    },
  • The server.tool() invocation that registers the 'helloTool' with its name, input schema, and handler function.
    server.tool(
      "helloTool",
      {
        message: z.string().optional().describe("Message to echo back. If not provided, returns a default greeting.")
      },
      async ({ message }) => {
        try {
          const responseMessage = message ? `You said: ${message}` : "Hello, World!";
          
          return {
            content: [
              {
                type: "text",
                text: responseMessage
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error in hello tool: ${error instanceof Error ? error.message : String(error)}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • The exported registerHelloTool function that sets up and registers the helloTool on the MCP server instance.
    export function registerHelloTool(server: McpServer): void {
      console.error('Registering Hello World tool...');
      
      // Tool to echo a message or respond with "Hello, World!"
      server.tool(
        "helloTool",
        {
          message: z.string().optional().describe("Message to echo back. If not provided, returns a default greeting.")
        },
        async ({ message }) => {
          try {
            const responseMessage = message ? `You said: ${message}` : "Hello, World!";
            
            return {
              content: [
                {
                  type: "text",
                  text: responseMessage
                }
              ]
            };
          } catch (error) {
            return {
              content: [
                {
                  type: "text",
                  text: `Error in hello tool: ${error instanceof Error ? error.message : String(error)}`
                }
              ],
              isError: true
            };
          }
        }
      );
      
      console.error('Hello World tool registered successfully');
    }
  • src/index.ts:21-21 (registration)
    The call to registerHelloTool during the main server initialization in the entry point file.
    registerHelloTool(server);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/snoopdave/mcp-hello-world-ts'

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