Skip to main content
Glama
mazah81-gif

TypeScript MCP Server Boilerplate

by mazah81-gif

greeting

Generate personalized greetings in multiple languages including English, Spanish, Korean, Japanese, and Chinese by providing a name and preferred language.

Instructions

Greet a user in their specified language

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the person to greet
languageYesThe language for the greeting

Implementation Reference

  • The handler function for the 'greeting' tool. It takes name and language parameters, maps languages to greeting strings, and returns a text content block with the appropriate greeting.
    async ({ name, language }: { name: string; language: 'korean' | 'english' | 'spanish' | 'japanese' | 'chinese' }) => {
        const greetings: Record<string, string> = {
            korean: `안녕하세요, ${name}님!`,
            english: `Hello, ${name}!`,
            spanish: `¡Hola, ${name}!`,
            japanese: `こんにちは、${name}さん!`,
            chinese: `你好,${name}!`
        }
    
        return {
            content: [
                {
                    type: 'text',
                    text: greetings[language]
                }
            ]
        }
    }
  • Input schema for the 'greeting' tool using Zod, defining 'name' as string and 'language' as enum of supported languages.
        name: z.string().describe('The name of the person to greet'),
        language: z.enum(['korean', 'english', 'spanish', 'japanese', 'chinese']).describe('The language for the greeting')
    },
  • src/index.ts:23-48 (registration)
    Registration of the 'greeting' tool on the MCP server using server.tool, specifying name, description, input schema, and handler function.
    server.tool(
        'greeting',
        'Greet a user in their specified language',
        {
            name: z.string().describe('The name of the person to greet'),
            language: z.enum(['korean', 'english', 'spanish', 'japanese', 'chinese']).describe('The language for the greeting')
        },
        async ({ name, language }: { name: string; language: 'korean' | 'english' | 'spanish' | 'japanese' | 'chinese' }) => {
            const greetings: Record<string, string> = {
                korean: `안녕하세요, ${name}님!`,
                english: `Hello, ${name}!`,
                spanish: `¡Hola, ${name}!`,
                japanese: `こんにちは、${name}さん!`,
                chinese: `你好,${name}!`
            }
    
            return {
                content: [
                    {
                        type: 'text',
                        text: greetings[language]
                    }
                ]
            }
        }
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool's function but doesn't describe what happens when invoked—such as whether it returns a string, logs the greeting, or has side effects. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 waste. It's front-loaded with the core purpose and includes essential context about language specification. Every word earns its place, making it highly concise and well-structured.

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 (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavior and usage context. Without annotations or output schema, more behavioral transparency would improve completeness for agent invocation.

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%, so the schema already documents both parameters ('name' and 'language') with descriptions and an enum for 'language'. The description adds no additional parameter semantics beyond implying language customization. Baseline 3 is appropriate when the schema handles most of the documentation.

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 clearly states the verb ('Greet') and resource ('a user'), specifying the action and target. It adds meaningful context about language customization, which distinguishes it from generic greeting tools. However, it doesn't explicitly differentiate from sibling tools like 'calculator' or 'image_generation' since those are unrelated functions.

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 prerequisites, constraints, or scenarios where this tool is preferred over other methods of greeting. With unrelated sibling tools, explicit differentiation isn't needed, but general usage context is missing.

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/mazah81-gif/my-mcp-server-2025'

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