Skip to main content
Glama
luquitared

MCP Server Boilerplate

by luquitared

hello-world

Generate a personalized greeting by providing a user name. This tool demonstrates basic MCP server functionality for creating custom AI assistant integrations.

Instructions

Say hello to the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the user

Implementation Reference

  • The handler function for the 'hello-world' tool. It receives a 'name' parameter and returns a text content block with the greeting 'Hello ${name}'.
    async ({ name }) => {
      const response = `Hello ${name}`;
    
      return {
        content: [
          {
            type: "text",
            text: response,
          },
        ],
      };
    }
  • 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:13-31 (registration)
    Registration of the 'hello-world' tool on the MCP server, specifying name, description, input schema, and handler function.
    server.tool(
      "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. It states 'Say hello to the user', which implies a read-only or informational output, but doesn't disclose behavioral traits like whether it requires authentication, has side effects, or how it interacts with the user. It's minimal and lacks transparency for an agent.

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 is appropriately sized and front-loaded, making it easy to parse quickly. Every word earns its place without redundancy.

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

Completeness2/5

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

Given the tool's simplicity (1 parameter, no annotations, no output schema), the description is incomplete. It doesn't explain what 'say hello' means in practice, such as the format of the greeting or any return values. For even a simple tool, more context would help an agent understand its behavior.

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 1 parameter with 100% description coverage ('The name of the user'), so the schema does the heavy lifting. The description adds no meaning beyond the schema, as it doesn't explain parameter usage or constraints. Baseline 3 is appropriate given high schema coverage.

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

Purpose3/5

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

The description 'Say hello to the user' states a clear action (say hello) but is vague about the resource or mechanism. It doesn't distinguish from the sibling tool 'get-mcp-docs', which appears unrelated. The purpose is understandable but lacks specificity about what 'say hello' entails operationally.

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 exclusions. The sibling tool 'get-mcp-docs' seems unrelated, but no comparison or usage scenarios are offered.

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/luquitared/mcp-animator'

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