Skip to main content
Glama
currentspace

Bootstrap MCP Server

by currentspace

hello_world

Generate a greeting message by providing a name input. This tool demonstrates basic functionality for building MCP servers.

Instructions

A simple hello world tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName to greet

Implementation Reference

  • The handleHelloWorld method implements the core logic for the 'hello_world' tool, extracting the 'name' from args and returning a formatted greeting message.
    private handleHelloWorld(args: any) {
        const name = args.name as string
        return {
            content: [
                {
                    type: 'text',
                    text: `Hello, ${name}! Welcome to the Bootstrap MCP Server.`,
                },
            ],
        }
    }
  • The ToolSchema definition for 'hello_world', including name, description, and inputSchema requiring a 'name' string property.
    {
        name: 'hello_world',
        description: 'A simple hello world tool',
        inputSchema: {
            type: 'object',
            properties: {
                name: {
                    type: 'string',
                    description: 'Name to greet',
                },
            },
            required: ['name'],
        },
    },
  • src/server.ts:82-83 (registration)
    The switch case in the CallToolRequestSchema handler that registers and dispatches 'hello_world' tool calls to the handleHelloWorld method.
    case 'hello_world':
        return this.handleHelloWorld(args)
  • src/server.ts:72-74 (registration)
    The ListToolsRequestSchema handler that registers the list of tools, including 'hello_world' via the TOOLS array.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: TOOLS,
    }))
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. The description offers no information about what the tool actually does, how it behaves, what it returns, or any operational characteristics. 'Simple hello world tool' doesn't explain whether this performs a greeting action, displays output, or has any side effects.

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 four words, this is a case of under-specification rather than effective conciseness. The description fails to communicate essential information about the tool's purpose and behavior. Every sentence should earn its place, and this single sentence provides minimal value beyond what's already implied by the tool name.

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 almost no useful information, this is completely inadequate. The description doesn't explain what the tool does, when to use it, what it returns, or how it behaves. For even a simple tool with one parameter, this description fails to provide the minimal contextual information needed for an agent to understand and use the tool effectively.

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' well-documented as 'Name to greet'. The description adds no additional parameter information beyond what the schema provides. With complete schema coverage, the baseline score of 3 is appropriate since the schema does the heavy lifting for parameter documentation.

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 a tautology that essentially restates the tool name 'hello_world' without specifying what the tool actually does. It mentions 'hello world' which implies greeting functionality, but doesn't clearly state the verb+resource combination or distinguish this from sibling tools like 'echo' or 'get_time'.

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 versus alternatives. There's no mention of appropriate contexts, prerequisites, or comparisons to sibling tools like 'echo' or 'get_time'. The agent receives no help in determining when this specific greeting tool should be selected.

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/currentspace/bootstrap_mcp'

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