Skip to main content
Glama

hello

Generate personalized greeting messages by providing a name. This tool creates custom hello world outputs for testing and demonstration purposes.

Instructions

A simple hello world tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name to say hello to

Implementation Reference

  • The handler for the 'hello' tool. It returns a text content block with a personalized greeting message using the 'name' argument or defaults to 'world'.
    case "hello": {
      return {
        content: [
          {
            type: "text",
            text: `Hello, ${args?.name || "world"}!`,
          },
        ],
      };
    }
  • The input schema for the 'hello' tool, defining a required 'name' property of type string.
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "The name to say hello to",
        },
      },
      required: ["name"],
    },
  • The registration entry for the 'hello' tool in the tools list returned by ListToolsRequestHandler, including name, description, and input schema.
      name: "hello",
      description: "A simple hello world tool",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The name to say hello to",
          },
        },
        required: ["name"],
      },
    },
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides none. 'Simple hello world tool' doesn't indicate whether this is a read operation, write operation, whether it has side effects, what it returns, or any behavioral characteristics. The description is completely inadequate for a tool with unknown 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 is extremely concise at just 4 words. While it's under-specified, every word earns its place - 'simple' sets expectations, 'hello world' describes the category, and 'tool' identifies the artifact type. There's no wasted verbiage or unnecessary elaboration.

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?

Given no annotations, no output schema, and a description that provides minimal information, this description is completely inadequate. For a tool with one required parameter and unknown behavior, the description should explain what the tool does, what it returns, and how the parameter affects the outcome. The current description leaves all critical context gaps unfilled.

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% (the single parameter 'name' has a clear description), so the baseline score is 3. The tool description adds no parameter information beyond what's already in the schema - it doesn't explain the parameter's role in the 'hello world' context or provide any additional semantic meaning.

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 'A simple hello world tool' is tautological - it essentially restates the tool name 'hello' with minimal additional meaning. While it implies a greeting function, it doesn't specify what the tool actually does (e.g., returns a greeting message, logs a greeting, triggers a notification). The description fails to distinguish this tool from its siblings which are all image/generation-related tools.

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 absolutely no guidance about when to use this tool versus alternatives. There's no mention of context, prerequisites, or comparison to sibling tools (all of which are image/generation related, making this tool's purpose unclear in relation to them). The agent receives no help in determining appropriate use cases.

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/Aeven-AI/mcp-nanobanana'

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