Skip to main content
Glama
devbrother2024

TypeScript MCP Server Boilerplate

greet

Generate personalized greetings in multiple languages by providing a name and preferred language. This tool helps create welcome messages for users in applications built with the TypeScript MCP Server Boilerplate.

Instructions

이름과 언어를 입력하면 인사말을 반환합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes인사할 사람의 이름
languageNo인사 언어 (기본값: en)en

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes인사말

Implementation Reference

  • The 'greet' tool registration and handler implementation.
    server.registerTool(
        'greet',
        {
            description: '이름과 언어를 입력하면 인사말을 반환합니다.',
            inputSchema: z.object({
                name: z.string().describe('인사할 사람의 이름'),
                language: z
                    .enum(['ko', 'en'])
                    .optional()
                    .default('en')
                    .describe('인사 언어 (기본값: en)')
            }),
            outputSchema: z.object({
                content: z
                    .array(
                        z.object({
                            type: z.literal('text'),
                            text: z.string().describe('인사말')
                        })
                    )
                    .describe('인사말')
            })
        },
        async ({ name, language }) => {
            const greeting =
                language === 'ko'
                    ? `안녕하세요, ${name}님!`
                    : `Hey there, ${name}! 👋 Nice to meet you!`
    
            return {
                content: [
                    {
                        type: 'text' as const,
                        text: greeting
                    }
                ],
                structuredContent: {
                    content: [
                        {
                            type: 'text' as const,
                            text: greeting
                        }
                    ]
                }
            }
        }
    )
Behavior2/5

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

No annotations are provided, placing the full disclosure burden on the description, yet it fails to mention behavioral traits such as whether the operation is read-only, idempotent, or stateless. It also does not clarify that the greeting is generated text rather than fetched from an external service, though the existence of an output schema mitigates the need for return value description.

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 consists of a single, highly efficient sentence that front-loads the core functionality without tautology or redundant phrasing. Every word contributes to understanding the input-output relationship, making it appropriately 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 low complexity (two simple parameters, one required), complete schema coverage, and the existence of an output schema, the description provides sufficient context for correct invocation. However, it could be improved by mentioning safety characteristics or confirming the localized nature of the output given the Korean-language context.

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?

With 100% schema description coverage, the parameters (name and language) are fully documented in the input schema, including the default value for language. The description merely references them ('이름과 언어') without adding semantic context, syntax details, or usage examples beyond what the schema already provides, meeting the baseline for high-coverage schemas.

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 uses the specific verb '반환합니다' (returns) with the resource '인사말' (greeting), clearly stating the tool generates a greeting message when given inputs. It effectively distinguishes itself from siblings like calc, generate-image, and geocode, which perform distinct functions (mathematics, image generation, geocoding).

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?

The description explains what the tool does but does not provide explicit guidance on when to prefer it over alternatives or specific use cases (e.g., when templated greetings are needed). Usage is implied by the tool name and parameter names, but no explicit when/when-not conditions are stated.

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/devbrother2024/my-mcp-server-260402'

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