Skip to main content
Glama
CaptainCrouton89

MCP Server Boilerplate

hello-world

Generate personalized greetings by providing a user name, demonstrating basic tool functionality in MCP server development.

Instructions

Say hello to the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the user

Implementation Reference

  • The asynchronous handler function for the 'hello-world' tool that receives a 'name' parameter and returns a text content block with a greeting message.
    async ({ name }) => {
      const response = `Hello ${name}`;
    
      return {
        content: [
          {
            type: "text",
            text: response,
          },
        ],
      };
    }
  • The input schema for the 'hello-world' tool, defining a required 'name' string parameter.
    {
      name: z.string().describe("The name of the user"),
    },
  • src/index.ts:14-31 (registration)
    The registration of the 'hello-world' tool on the MCP server using server.tool(), specifying the tool name, description, input schema, and handler function.
      "hello-world",
      "Say hello to the user",
      {
        name: z.string().describe("The name of the user"),
      },
      async ({ name }) => {
        const response = `Hello ${name}`;
    
        return {
          content: [
            {
              type: "text",
              text: response,
            },
          ],
        };
      }
    );
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. 'Say hello to the user' implies a read-only, non-destructive operation, but it doesn't specify output format, side effects, or any constraints (e.g., rate limits, authentication needs). 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 'Say hello to the user' is a single, efficient sentence that directly conveys the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero waste, making it easy for an agent to parse quickly.

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 simplicity (one parameter, no annotations, no output schema), the description is minimally adequate. It states what the tool does but lacks details on output, usage context, or behavioral traits. For a basic greeting tool, this might suffice, but it doesn't provide complete guidance for optimal 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?

The input schema has 100% description coverage, with the single parameter 'name' documented as 'The name of the user'. The description doesn't add any parameter details beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 the user' clearly states the tool's purpose with a specific verb ('Say hello') and target ('to the user'). It distinguishes itself from the sibling tool 'get-mcp-docs' by focusing on greeting rather than documentation retrieval. However, it doesn't explicitly mention the resource being acted upon (e.g., generating a greeting message).

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. There's no mention of context, prerequisites, or comparison with the sibling tool 'get-mcp-docs'. The agent must infer usage based solely on 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/CaptainCrouton89/mcp-reasoning'

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