Skip to main content
Glama
gemyago

HelloWorld MCP Server

by gemyago

hello

Generate personalized greetings by inputting a name to receive a customized hello message from the HelloWorld MCP Server.

Instructions

Say hello to someone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the person to greetWorld

Implementation Reference

  • Handler logic for the 'hello' tool, extracting the name parameter and returning a greeting text response.
    case 'hello': {
      const targetName = (args as { name?: string }).name || 'World';
      return {
        content: [
          {
            type: 'text',
            text: `Hello, ${targetName}! 👋 Welcome to the HelloWorld MCP server!`,
          },
        ],
      };
    }
  • Input schema and metadata for the 'hello' tool, defined in the ListTools response.
    {
      name: 'hello',
      description: 'Say hello to someone',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'The name of the person to greet',
            default: 'World',
          },
        },
      },
    },
  • src/index.ts:25-62 (registration)
    Registration of tools including 'hello' via the ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: 'hello',
            description: 'Say hello to someone',
            inputSchema: {
              type: 'object',
              properties: {
                name: {
                  type: 'string',
                  description: 'The name of the person to greet',
                  default: 'World',
                },
              },
            },
          },
          {
            name: 'add',
            description: 'Add two numbers together',
            inputSchema: {
              type: 'object',
              properties: {
                a: {
                  type: 'number',
                  description: 'First number',
                },
                b: {
                  type: 'number',
                  description: 'Second number',
                },
              },
              required: ['a', 'b'],
            },
          },
        ],
      };
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Say hello to someone' implies a read-only, non-destructive action, but it doesn't specify whether this requires authentication, has rate limits, returns structured data, or how the greeting is delivered (e.g., console output, API response). For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple greeting tool. Every word earns its place without redundancy or unnecessary elaboration.

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

Completeness3/5

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

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavioral traits, usage context, or output format. For such a simple tool, this might be sufficient, but it doesn't provide complete guidance for optimal agent use.

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?

Schema description coverage is 100%, with the single parameter 'name' fully documented in the schema as 'The name of the person to greet' with a default value. The description doesn't add any parameter details beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without extra value.

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

Purpose4/5

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

The description 'Say hello to someone' clearly states the tool's purpose with a specific verb ('say hello') and target ('to someone'). It distinguishes from the sibling tool 'add' which likely performs a different function. However, it doesn't specify the exact output format or delivery mechanism, keeping it from a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or comparisons with the sibling tool 'add'. The agent must infer usage solely from the tool name and description without explicit direction.

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/gemyago/typescript-mcp-boilerplate'

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