Skip to main content
Glama
MatthewDailey

MCP Starter Server

hello_tool

Generate personalized greetings by inputting a name. Built on the MCP Starter Server, this tool simplifies interaction with AI assistant tools using the ModelContextProtocol.

Instructions

Hello tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the person to greet

Implementation Reference

  • index.ts:24-34 (handler)
    The handler function that logs the name and returns a text response greeting the person by name.
    async ({ name }) => {
      console.error("Hello tool", { name });
      return {
        content: [
          {
            type: "text",
            text: `Hello, ${name}!`,
          },
        ],
      };
    }
  • Input schema defining the 'name' parameter as a string with description.
    {
      name: z.string().describe("The name of the person to greet"),
    },
  • index.ts:18-35 (registration)
    Registration of the 'hello_tool' using server.tool, including name, description, input schema, and handler.
    server.tool(
      "hello_tool",
      "Hello tool",
      {
        name: z.string().describe("The name of the person to greet"),
      },
      async ({ name }) => {
        console.error("Hello tool", { name });
        return {
          content: [
            {
              type: "text",
              text: `Hello, ${name}!`,
            },
          ],
        };
      }
    );
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Hello tool' reveals nothing about whether this performs read/write operations, requires authentication, has side effects, rate limits, or what the response format might be. It's completely inadequate for behavioral understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just two words, this represents under-specification rather than effective brevity. The description fails to provide any meaningful information that would help an AI agent understand or use the tool properly, making it inefficient despite its short length.

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

Completeness1/5

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

For a tool with no annotations and no output schema, the description 'Hello tool' is completely inadequate. It provides no information about what the tool does, how it behaves, what it returns, or any operational context. The description fails to compensate for the lack of structured metadata.

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%, with the single parameter 'name' clearly documented as 'The name of the person to greet'. The description adds no additional parameter information beyond what's in the schema, but with complete schema coverage, the baseline score of 3 is appropriate.

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

Purpose2/5

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

The description 'Hello tool' is a tautology that essentially restates the tool name without specifying what it actually does. While the name 'hello_tool' suggests a greeting function, the description fails to articulate a clear verb+resource combination or any specific purpose beyond the obvious implication from the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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, what context it's appropriate for, or any prerequisites. With no sibling tools mentioned, there's no need to differentiate from alternatives, but the description still offers zero usage instructions or contextual hints.

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

Related 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/MatthewDailey/mcp-starter'

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