Skip to main content
Glama
ricleedo

MCP Server Boilerplate

by ricleedo

hello-world

Generate personalized greetings by providing a user name. This tool demonstrates basic functionality for MCP server development templates.

Instructions

Say hello to the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the user

Implementation Reference

  • The async handler function for the "hello-world" tool. It takes a 'name' parameter and returns a text response greeting the user.
    async ({ name }) => {
      const response = `Hello ${name}`;
    
      return {
        content: [
          {
            type: "text",
            text: response,
          },
        ],
      };
    }
  • Zod input schema defining the 'name' parameter for the "hello-world" tool.
    {
      name: z.string().describe("The name of the user"),
    },
  • src/index.ts:14-31 (registration)
    Registration of the "hello-world" tool using server.tool(), including name, description, schema, and handler.
      "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 action, but it doesn't specify output format, side effects, or any constraints like rate limits. For a tool with zero 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 'Say hello to the user' is a single, clear sentence with zero wasted words. It is appropriately sized for a simple tool and front-loads the core purpose effectively.

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 parameter, no output schema, no annotations), the description is minimally adequate. It states the purpose but lacks details on output, usage context, or behavioral traits. Without an output schema, the description should ideally explain return values, but for such a simple tool, it meets the bare minimum.

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 adds no additional parameter information beyond what the schema provides. According to the rules, when schema_description_coverage is high (>80%), the baseline score is 3 even with no param info in the description.

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 from the sibling tool 'get-mcp-docs' which presumably retrieves documentation. However, it doesn't specify the exact output format or mechanism, keeping it at a 4 rather than a perfect 5.

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 is no mention of context, prerequisites, or comparison to the sibling tool 'get-mcp-docs'. It simply states what the tool does without indicating appropriate usage scenarios.

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/ricleedo/reddit-mcp'

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